Bart, thanks a lot! Your 2 commands are the ones I used and the settings are similar. Indeed it does make sense to me what Jeroen is suggesting: i'll try to get another pc with a new .Net installation. Cheers, Mauro
----Original Message Follows---- From: Bart Samwel <[EMAIL PROTECTED]> To: "Jeroen T. Vermeulen" <[EMAIL PROTECTED]> CC: mauro castelli <[EMAIL PROTECTED]>, [email protected] Subject: Re: [libpqxx-general] Errors building libpqxx with .Net2003 on windows XP SP2. Date: Fri, 11 Aug 2006 09:55:22 +0200 Hi mauro, Jeroen, On a sidenote, I promised I'd try to compile things when I got back. The SVN version builds perfectly for me: COMMAND 1: tools\template2mak.py win32\vc-libpqxx.mak.template > win32\vc-libpqxx.mak COMMAND 2: NMAKE /f win32\vc-libpqxx.mak STATIC Of course, this is with the proper paths in the config files. My "win32\common" file has these settings: PGSQLSRC="D:\Src\postgresql-8.1.3\src" LIBPATH1="$(PGSQLSRC)/interfaces/libpq/Release" LIBPATH2="$(PGSQLSRC)/interfaces/libpq/Debug" I tried it with the makefile supplied by Jeroen on pqxx.org as well, and that works fine for me too. Cheers, Bart Jeroen T. Vermeulen wrote: >On Fri, August 11, 2006 04:56, mauro castelli wrote: >>Jeroen, >>nothing changed, again. > >Argh! > >But... > >>D:\DriveF\DB\Downloads\postgresql\libpqxx-2.6.7>nmake /f >>win32/vc-libpqxx.mak STATICRELEASE >> >>Microsoft (R) Program Maintenance Utility versione 7.00.9466 >>Copyright (C) Microsoft Corporation. Tutti i diritti riservati. >> >> cl.exe /nologo /W3 /GX /FD /GR /c /I "include\pqxx" /I "include" >>/I >>"D: >>\DriveF\DB\Downloads\postgresql\source\postgresql-8.1.4\src\i >>nclude" /I "D:\DriveF\DB\Downloads\postgresql\source\postgres >>ql-8.1.4\src/interfaces/libpq" /D PGSTD="std" /D "WIN32" /D "_MBCS" /D >>"_WINDOW >>S" /D "PQXX_INTERNAL" /MD /D "_LIB" /D "NDEBUG" /Fo"ObjStaticRelease\\" >>/Fd"ObjS >>taticRelease\\" src/binarystring.cxx >>NMAKE : errore irreversibile U1077: "cl.exe" : codice restituito >>"0xc0000135" >>Stop. > >Unless my Italian is even worse than I think, the only message you're >getting here is that cl.exe (i.e. the compiler, not nmake!) returned an >error code 0xc0000135. > >>From what I can find on the Web, this error code means that some DLL was >not found. And this is just a regular compile command, not a link >command, so it's not about libpq.dll or anything like that. I think that >this means the compiler itself is missing a DLL that it needs in order to >run. > >So my impression is that something went wrong with your compiler >installation, not with libpqxx itself. That's probably also why there is >no useful error message. > >I wonder if maybe the problem could be with the language support in the >compiler... Can you try running nmake and the compiler in English? > > >>- line 241 of file vc-libpqxx.mak: >> copy $(PGSQLSRC)\interfaces\libpq\release\libpq.dll $(OUTDIR) >> should be >> copy $(LIBPATH1)\libpq.dll $(OUTDIR) >> same for Debug, isn't it???? > >For your case that is fine, but I think it was done this way to make sure >that libpq.dll is really the release version and libpqd.dll is really the >debug version. With LIBPATH1 and LIBPATH2 that distinction is not so >clear. Maybe this part of the "common-sample" file needs a bit of >redesign. > > >Jeroen > > >_______________________________________________ >Libpqxx-general mailing list >[email protected] >http://gborg.postgresql.org/mailman/listinfo/libpqxx-general _________________________________________________________________ Condivi foto, pensieri ed altro ancora creando il tuo Blog su Windows Live Spaces ! http://discoverspaces.live.com/?loc=it-IT _______________________________________________ Libpqxx-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/libpqxx-general
