On Tue, Feb 4, 2014 at 3:24 AM, Thomas Jarosch <[email protected]> wrote: > Hi Chris, > > On Friday, 31. January 2014 17:35:15 Chris Morgan wrote: >> Alright, attached is a proof of concept patch, untested, for comments >> on the approach. > > what I'm wondering about is why this is needed at all. > Normally I just supply "-static" to gcc and it finds > the .a library files automatically. > > When you do a static build without the patch you sent, > how is your compiler invoked? > > 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. Chris -- libftdi - see http://www.intra2net.com/en/developer/libftdi for details. To unsubscribe send a mail to [email protected]
