Den 2010-09-04 16:21 skrev Charles Wilson: > On 9/4/2010 4:52 AM, Peter Rosin wrote: >> >> If you are using -lfoo, then you *must* use 'compile' as well as cl >> does not know about the -l option. So, I was thinking that 'compile' >> instead of just transforming -lfoo into foo.lib would walk the library >> search path (in the same order as cl would) and replace -lfoo with >> either of foo.lib or foo.dll.lib depending on which was found first >> and possibly also modified by any -static or -shared flags (also not >> supported by cl, so -static and -shared would have to be completely >> handled by 'compile' and would only affect -lfoo handling, at least >> in my current thinking). > > Remember that -static and -shared, the gcc options, are not antonyms: > > `-static' > On systems that support dynamic linking, this prevents linking > with the shared libraries. > > `-shared' > Produce a shared object which can then be linked with other > objects to form an executable.
Oh *blush*, I slipped there. I blame libtool and that it handles all that gunk so that I don't have to :-) > I have no objections anymore, but I can't approve it. Good. And thanks for the useful discussion. Cheers, Peter
