Re: MS lib program in msys

2007-01-21 Thread Ralf Wildenhues
Hello Howard, Chris, apologies for the delay. * Howard Chu wrote on Mon, Jan 08, 2007 at 08:45:21PM CET: > > Pretty sure "-" has been valid since at least Win95. Definitely this > should be changed. OK, on my rather oldish installation it seems to work as well. I have applied the patches below

Re: MS lib program in msys

2007-01-08 Thread Howard Chu
Ralf Wildenhues wrote: Hello Christopher, Thanks for the report. * Christopher Hulbert wrote on Fri, Jan 05, 2007 at 04:10:18PM CET: Libtool uses MS's lib program when not using gcc in windows. On msys "lib /out:.libs/liba.lib" is translated to "lib C:\msys1.0\OUT;.libs\liba.lib". I'm not s

Re: MS lib program in msys

2007-01-08 Thread Christopher Hulbert
On 1/8/07, Ralf Wildenhues <[EMAIL PROTECTED]> wrote: Hello Christopher, Thanks for the report. * Christopher Hulbert wrote on Fri, Jan 05, 2007 at 04:10:18PM CET: > Libtool uses MS's lib program when not using gcc in windows. On msys > "lib /out:.libs/liba.lib" is translated to "lib > C:\msys1

Re: MS lib program in msys

2007-01-08 Thread Ralf Wildenhues
Hello Christopher, Thanks for the report. * Christopher Hulbert wrote on Fri, Jan 05, 2007 at 04:10:18PM CET: > Libtool uses MS's lib program when not using gcc in windows. On msys > "lib /out:.libs/liba.lib" is translated to "lib > C:\msys1.0\OUT;.libs\liba.lib". I'm not sure when lib (or window

MS lib program in msys

2007-01-05 Thread Christopher Hulbert
Libtool uses MS's lib program when not using gcc in windows. On msys "lib /out:.libs/liba.lib" is translated to "lib C:\msys1.0\OUT;.libs\liba.lib". I'm not sure when lib (or windows) started accepting "-" for options, but "lib -out" fixes the problem on Windows XP. Would there be any objection to

MS

2004-10-27 Thread Dr . Mahmoud Sa'id
My names are Dr. Mahmoud Sa'id. I am an Iraqi indigene. I am presently a member of the Iraq Project and Contracting Office (PCO) formerly known as the Program Management Office (PMO) in Iraq. The responsibility of this said committee as it is declared on section 3 (1) (Contracting Authority) of

MS Encarta Encyclopedia Delux 2004 $80 belmont

2004-05-19 Thread Letha Langford
Loads of cool soft at incredibly low prices Windows XP Professional + Office XP Professional for as low as $80 Order here The stock is limited The offer is valid till May, 10 Hurry! gone transpondcrocodilian effluvium lacecassandra tipple aeneasbutane glenda destinateail contiguous distantd

MS Encarta Encyclopedia Standart 2004 clearance alienate

2004-04-28 Thread Glen Dubois
Uns*cribe He*re attrition flabbycowry obsolescent rackfreest carnal lancebacteria wharton impudentshoulder keep sailfishkilo strove documentationcomplicity dint dozensyllogistic intend efferentcartesian thinnish polkadotrejecter unidimensional seventiethshunt edging begunex anaerobic aidbi

Re: MinGW link against an MS Windows import library

2004-04-15 Thread Bill Jones
I don't think that linking directly against a DLL under Windows is a good idea (or even possible). From http://blogs.msdn.com/oldnewthing/archive/2004/01/12/57833.aspx it would appear that the LIB file should be used to account for any "decorations" added to the exports. wtj Earnie Boyd wrot

Re: MinGW link against an MS Windows import library

2004-04-14 Thread Tim Van Holder
ies in the .lib file list 'KERNEL32.DLL' as name), but those are provided as .a by MingW, so that's not much of a help either (and I'm fairly certain non-MS import libraries don't have the same 'feature'). ___ Libto

Re: MinGW link against an MS Windows import library

2004-04-14 Thread Bob Friesenhahn
On Wed, 14 Apr 2004, Earnie Boyd wrote: > > > More or less the same. There may be a few differences. However, > binutils have been able to read the MS produced .lib files for some > years now. So all that is needed is for libtool to accept .lib as an extension and for libto

Re: MinGW link against an MS Windows import library

2004-04-14 Thread Earnie Boyd
suggests that the format is Unix ar format. More or less the same. There may be a few differences. However, binutils have been able to read the MS produced .lib files for some years now. Earnie. -- http://www.mingw.org http://sourceforge.net/projects/mingw https://sourceforge.net/donate/index.php

Re: MinGW link against an MS Windows import library

2004-04-14 Thread Bob Friesenhahn
On Wed, 14 Apr 2004, Bill Jones wrote: > I have considered this but do not see it as a practical solution. I do > not think that it should be the responsibility of every developer to > make a copy of a file simply because the extension is not what libtool > likes. The .lib extension is a valid e

Re: MinGW link against an MS Windows import library

2004-04-14 Thread Bill Jones
I have considered this but do not see it as a practical solution. I do not think that it should be the responsibility of every developer to make a copy of a file simply because the extension is not what libtool likes. The .lib extension is a valid extension to Windows and it seems more approp

Re: MinGW link against an MS Windows import library

2004-04-14 Thread Bill Jones
Thanks, but I tried this without success as noted in attempt 4) in my original post. It is my understanding that you should not link directly against a Windows .dll file, but instead link against the import library (.lib). In any event, "-Lpath -lfoo" does produce my DLL when path was set to

Re: MinGW link against an MS Windows import library

2004-04-14 Thread Earnie Boyd
Tim Van Holder wrote: Bill Jones wrote: So the basic question is how do I specify a static import library with a *.lib extension to be used by libtool for resolving the symbols provided by a non-libtool DLL when building a dependent DLL with libtool? The trivial solution is of course to make

Re: MinGW link against an MS Windows import library

2004-04-13 Thread Tim Van Holder
Bill Jones wrote: So the basic question is how do I specify a static import library with a *.lib extension to be used by libtool for resolving the symbols provided by a non-libtool DLL when building a dependent DLL with libtool? The trivial solution is of course to make a copy of the third-party

MinGW link against an MS Windows import library

2004-04-13 Thread Bill Jones
I could not find any recent discussion of this topic in the list archives. I am trying to use libtool to create a DLL which requires linking my objects against a non-libtool MS Windows import library provided by a 3rd party vendor. The import library has the ".lib" extension an

Re: Win32: Autotools/libtool and MS VC++?

2001-01-24 Thread Morten Eriksen
Marc van Woerkom <[EMAIL PROTECTED]> writes: > [...] what happens if one really wants to use the Microsoft C/C++ > compiler? One solution we've found to work well is to wrap the cl.exe compiler (and the linker) within a shell script that converts "UNIX-style" compiler arguments into what MSVC++

Re: Win32: Autotools/libtool and MS VC++?

2001-01-24 Thread Olly Betts
In message <[EMAIL PROTECTED]>, Greg Eisenhauer writes: >There is support for compiling with VC++ at least in the sense that cygpath >is called to fixup the source file names for the compiler. However, this >isn't done at the link stage and the path and file names embedded in the >*.la files are

Re: Win32: Autotools/libtool and MS VC++?

2001-01-24 Thread Greg Eisenhauer
X-Authentication-Warning: nil.science-factory.com: mvw set sender to [EMAIL PROTECTED] using -f From: Marc van Woerkom <[EMAIL PROTECTED]> Sender: [EMAIL PROTECTED] X-BeenThere: [EMAIL PROTECTED] X-Mailman-Version: 2.0 Precedence: bulk List-Help:

Win32: Autotools/libtool and MS VC++?

2001-01-24 Thread Marc van Woerkom
Dear list members, sadly I have been thrown in the JAVA trenches lately, (which would lead to the question of JAVA and Autotools :-) but for now I would need an information regarding Win32. Using Cygwin and the ported gcc seems supported rather well (autoconf, automake in the cygwin ports system