[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
libraries/*/options.c (ITS#564)
This is a MIME message. If you are reading this text, you may want to
consider changing to a mail reader or gateway that understands how to
properly handle MIME multipart messages.
--=_9CC494DB.3859F474
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
We are packaging libldap and liblber into one library.
Re: libldap/options.c and liblber/options.c
Our linker has heartburn because the two files have the same name.
Would it be possible to change the name of one or both of them to
something like
libldap/loptions.c
or
liblber/boptions.c
Would this change cause problems?
-Steve Sonntag
--=_9CC494DB.3859F474
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" http-equiv=3DContent-Type=
>
<META content=3D"MSHTML 5.00.2014.210" name=3DGENERATOR></HEAD>
<BODY style=3D"FONT: 8pt MS Sans Serif; MARGIN-LEFT: 2px; MARGIN-TOP: =
2px">
<DIV>We are packaging libldap and liblber into one library.</DIV>
<DIV> </DIV>
<DIV>Re: libldap/options.c and liblber/options.c</DIV>
<DIV> </DIV>
<DIV>Our linker has heartburn because the two files have the same =
name.</DIV>
<DIV> </DIV>
<DIV>Would it be possible to change the name of one or both of them =
to</DIV>
<DIV>something like</DIV>
<DIV> libldap/loptions.c</DIV>
<DIV> or</DIV>
<DIV> liblber/boptions.c</DIV>
<DIV> </DIV>
<DIV>Would this change cause problems?</DIV>
<DIV> </DIV>
<DIV>-Steve Sonntag</DIV></BODY></HTML>
--=_9CC494DB.3859F474--