libftdi Archives

Subject: Re: Re: Re: static linking against libftdi?

From: Chris Morgan <chmorgan@xxxxxxxxx>
To: "libftdi@xxxxxxxxxxxxxxxxxxxxxxx" <libftdi@xxxxxxxxxxxxxxxxxxxxxxx>
Date: Wed, 5 Feb 2014 11:03:46 -0500
On Wed, Feb 5, 2014 at 11:02 AM, Thomas Jarosch
<thomas.jarosch@xxxxxxxxxxxxx> wrote:
> On Tuesday, 4. February 2014 06:44:43 Chris Morgan wrote:
>> > You can see the command line arguments when you do a
>> >
>> >     make VERBOSE=1
>>
>> I haven't tried asking gcc to link everything statically as I just
>> wanted to link libftdi (and I'm linking in a boost library statically
>> as well by setting an option like in the solution Uwe posted above),
>> because the other users have libc available. From everything I've read
>> about cmake the way to link against a static library is to pass the
>> full path to the library. I was just hoping to help bake this into the
>> cmake scripts delivered by libftdi.
>
> ah ok, now I understand your use case. The patch seems fine by me,
> I've squeezed it in before the final libftdi 1.1 release.
>
> Cheers,
> Thomas

Did you end up making any changes to it? Let me test it here right now
before you ship anything, if thats possible.

Chris

--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx   

Current Thread