From: Merrill C. <mer...@ea...> - 2005-11-18 15:20:08
|
I am using the current minGW with the C++ Boost libraries. Boost builds its libraries in a number of formats. I using the static, multi-threaded versions. For linking, I tried using ld's -L option to specify the directory containing the Boost .lib files (without trailing /) and a -l option for each of the libraries I am referencing. The static Boost libraries have named of the form lib[libname].lib. They way I understand the -L and -l are supposed to work on Windows is that I would use -Ldirectory -llibname and ld automagically add the "lib" prefix and the ".lib" file extension--but that doesn't seem to happen. ld complains that it can't find -l[libname]. If I remove the -l and specify the full pathname of the library, it links just fine. How is ld's -L and -l options supposed to work on Windows? Merrill |
From: Keith M. <kei...@to...> - 2005-11-18 16:31:05
|
Merrill Cornish asked: > How is ld's -L and -l options supposed to work on Windows? -Ldir specifies a directory path name, where library files may be found, just like on *nix. -lNAME instructs the linker to search for libNAME.a, in any directory in the lib search path, also just like in *nix. I'm not sure if it extends the search to also look for libNAME.lib on Windoze. As you have discovered you can link to libNAME.lib by specifying its full path name explicitly. Try using `g++' to link C++ projects, or `gcc' for C, rather than using `ld' directly -- that is the GCC recommended procedure, and it may just invoke the magic you are looking for. Regards, Keith. |
From: Tor L. <tm...@ik...> - 2005-11-18 17:08:53
|
Keith MARSHALL writes: > -lNAME instructs the linker to search for libNAME.a, in any > directory in the lib search path, also just like in *nix. I'm > not sure if it extends the search to also look for libNAME.lib > on Windoze. This surely is documented somewhere, but I am pretty sure that, given -lNAME, ld looks for: libNAME.a libNAME.dll.a NAME.lib NAME.dll maybe also libNAME.lib and libNAME.dll. --tml |
From: Daniel A. <dan...@gm...> - 2005-11-18 17:02:34
|
T24gMTEvMTgvMDUsIEtlaXRoIE1BUlNIQUxMIDxrZWl0aC5tYXJzaGFsbEB0b3RhbC5jb20+IHdy b3RlOgo+IC1sTkFNRSBpbnN0cnVjdHMgdGhlIGxpbmtlciB0byBzZWFyY2ggZm9yIGxpYk5BTUUu YSwgaW4gYW55Cj4gZGlyZWN0b3J5IGluIHRoZSBsaWIgc2VhcmNoIHBhdGgsIGFsc28ganVzdCBs aWtlIGluICpuaXguICBJJ20KPiBub3Qgc3VyZSBpZiBpdCBleHRlbmRzIHRoZSBzZWFyY2ggdG8g YWxzbyBsb29rIGZvciBsaWJOQU1FLmxpYgo+IG9uIFdpbmRvemUuICBBcyB5b3UgaGF2ZSBkaXNj b3ZlcmVkIHlvdSBjYW4gbGluayB0byBsaWJOQU1FLmxpYgo+IGJ5IHNwZWNpZnlpbmcgaXRzIGZ1 bGwgcGF0aCBuYW1lIGV4cGxpY2l0bHkuCj4KCkkndmUgYmVlbiBhYmxlIHRvIHVzZSAtbE5BTUUg Zm9yICJsaWJOQU1FLmxpYiIgIGFuZCB5b3UgY2FuIGNlcnRhaW5seQpkbyAtbE5BTUUgZm9yIE5B TUUubGliLgoKWW91IHByb2JhYmx5IHNob3VsZG4ndCBiZSBsaW5raW5nIGRpcmVjdGx5IHRvIE1T VkMgLmxpYiBmaWxlcyB0aG91Z2gsCmNoZWNrIG91dCBodHRwOi8vd3d3Lm1pbmd3Lm9yZy9taW5n d2ZhcS5zaHRtbCNmYXEtbXN2Y2RsbAo= |
From: Sisyphus <sis...@op...> - 2005-11-18 22:04:22
|
----- Original Message ----- From: "Daniel Atallah" . > > You probably shouldn't be linking directly to MSVC .lib files though, > check out http://www.mingw.org/mingwfaq.shtml#faq-msvcdll The option of having gcc link directly to the MSVC-built dll (let's call it name.dll) with '-L/path/to/dll -lname' doesn't get a mention in the faq. Why so ? Every time I've tried that it has worked. (Admittedly, I've only tried it once :-) Cheers, Rob |
From: Michael G. <mg...@te...> - 2005-11-19 18:12:39
|
> > You probably shouldn't be linking directly to MSVC .lib files though, > > check out http://www.mingw.org/mingwfaq.shtml#faq-msvcdll >=20 > The option of having gcc link directly to the MSVC-built dll (let's call = it > name.dll) with '-L/path/to/dll -lname' doesn't get a mention in the faq. = Why > so ? Don't know. But you are aware it is a Wiki ?!? (you know what a Wiki is, don't you ?) So go ahead and improve what's there. Best, Michael =2D-=20 Vote against SPAM - see http://www.politik-digital.de/spam/ Michael Gerdau email: mg...@te... GPG-keys available on request or at public keyserver |
From: Tuomo L. <dj...@mb...> - 2005-11-19 19:15:15
|
Michael Gerdau wrote: >>>You probably shouldn't be linking directly to MSVC .lib files though, >>>check out http://www.mingw.org/mingwfaq.shtml#faq-msvcdll >> >>The option of having gcc link directly to the MSVC-built dll (let's call it >>name.dll) with '-L/path/to/dll -lname' doesn't get a mention in the faq. Why >>so ? > > Don't know. But you are aware it is a Wiki ?!? > (you know what a Wiki is, don't you ?) HYI http://www.mingw.org/mingwfaq.shtml#faq-msvcdll is *not* the Wiki FAQ. There seems to be two FAQs the HTML one (http://www.mingw.org/mingwfaq.shtml) and the Wiki one (http://www.mingw.org/MinGWiki/index.php/FAQ). It might be useful to have only one. Does anyone know if all the stuff found on HTML pages is duplicated in the Wiki? If so, maybe we should consider removing the HTML pages altogether? -- Tuomo ... Something is rotten in the state of confusion |
From: Keith M. <kei...@to...> - 2005-11-24 11:35:41
|
Tuomo Latto wrote: > There seems to be two FAQs > the HTML one (http://www.mingw.org/mingwfaq.shtml) > and the Wiki one (http://www.mingw.org/MinGWiki/index.php/FAQ). > It might be useful to have only one. Agreed. IMHO, the Wiki is the most logical repository for a unified FAQ. Any volunteers to merge the existing content of the HTML FAQ into the Wiki? Tuomo perhaps, since you've raised the issue? > Does anyone know if all the stuff found on HTML pages is > duplicated in the Wiki? Some possibly, but probably not all. > If so, maybe we should consider removing the HTML pages altogether? No, I don't agree here. The Wiki is a valuable community resource, but there is some content over which we should maintain tighter control. The separate HTML web content serves well for that, but it could almost certainly be better referenced from the Wiki. Regards, Keith. |
From: Julien L. <lec...@fr...> - 2005-11-24 20:19:59
|
> -----Original Message----- > From: min...@li... > [mailto:min...@li...] On Behalf Of > Keith MARSHALL > Sent: jeudi 24 novembre 2005 12:16 > To: min...@li... > Subject: [Mingw-users] Integrating Web and Wiki Content (was: > Using ld' -L and -l options) > > Tuomo Latto wrote: > > There seems to be two FAQs > > the HTML one (http://www.mingw.org/mingwfaq.shtml) > > and the Wiki one (http://www.mingw.org/MinGWiki/index.php/FAQ). > > It might be useful to have only one. > > Agreed. IMHO, the Wiki is the most logical repository for a > unified FAQ. Any volunteers to merge the existing content of > the HTML FAQ into the Wiki? Tuomo perhaps, since you've > raised the issue? It's also un unfinished "project" of mine. When I do have the time, I do work on the wiki. > > Does anyone know if all the stuff found on HTML pages is > duplicated in > > the Wiki? > > Some possibly, but probably not all. Yes, there is some duplication. The duplication is an artifact of trying to merge the FAQ with the wikiFAQ. Some licensing issues are also in both the wiki and the website. Licensing should not be removed from the website; since anybody could change wiki licensing page to anything they would want us to read. > > If so, maybe we should consider removing the HTML pages altogether? > > No, I don't agree here. The Wiki is a valuable community > resource, but there is some content over which we should > maintain tighter control. > The separate HTML web content serves well for that, but it > could almost certainly be better referenced from the Wiki. I also agree (with Keith), we should keep a FAQ independent of the wiki; with tighter control, even if contents are duplicated. Some content from the website FAQ could be removed though; pointing to wiki FAQ instead (ie: JNI DLL stuff...) Julien |
From: Keith M. <kei...@to...> - 2005-11-25 16:10:53
|
Julien Lecomte wrote: > I also agree (with Keith), we should keep a FAQ independent of > the wiki; with tighter control, even if contents are duplicated. > Some content from the website FAQ could be removed though; pointing > to wiki FAQ instead (ie: JNI DLL stuff...) Oh, I wasn't suggesting that we should keep two FAQs; I think the Wiki is the correct arena in which to maintain a single unified FAQ. There is some content -- details of licensing terms an obvious case in point -- where we need to retain tighter control than the Wiki allows. In the case of a question about licensing, for example, I think the FAQ, in the Wiki, should display the question, and a brief answer directing the reader, through a link, to the more controlled HTML content, where an in-depth descriptive document provides the detail. There really should be no reason for duplication, IMHO. Regards, Keith |
From: Brian D. <br...@de...> - 2005-11-25 23:21:23
|
Keith MARSHALL wrote: > There is some content -- details of licensing terms an obvious case > in point -- where we need to retain tighter control than the Wiki > allows. In the case of a question about licensing, for example, I > think the FAQ, in the Wiki, should display the question, and a brief Wouldn't it just be easier to mark certain pages on the wiki as 'locked' so that they can only be edited by administrators? Surely that would be easier than maintaining the information in two places. Note that I have no idea about the capabilities of the particular wiki software used, so it may not be possible... but most wikis have this feature. Brian |
From: Earnie B. <ea...@pr...> - 2005-11-27 19:28:58
|
Quoting Brian Dessent <br...@de...>: > Keith MARSHALL wrote: > >> There is some content -- details of licensing terms an obvious case >> in point -- where we need to retain tighter control than the Wiki >> allows. In the case of a question about licensing, for example, I >> think the FAQ, in the Wiki, should display the question, and a brief > > Wouldn't it just be easier to mark certain pages on the wiki as 'locked' > so that they can only be edited by administrators? Surely that would be > easier than maintaining the information in two places. Note that I have > no idea about the capabilities of the particular wiki software used, so > it may not be possible... but most wikis have this feature. > I certainly have used others Wiki to obtain information that presents more nicely. I don't know about how the admin or user updates happen. Some require an administrator to review the contributions before they become public. Kind Regards, Earnie Boyd For all your online shopping needs http://shop.siebunlimited.com. Register an account online and receive a 10% discount on your first purchase. |
From: Brian D. <br...@de...> - 2005-11-18 19:29:57
|
Tor Lillqvist wrote: > This surely is documented somewhere, but I am pretty sure that, given > -lNAME, ld looks for: http://sourceware.org/binutils/docs-2.16/ld/WIN32.html#index-direct-linking-to-a-dll-527 |