Re: [pgadmin-hackers] Building wxWindows on MacOS X
Hi Just for the record in case other stumble over the same problem (since you meanwhile used a newer wx snapshot) You should either get CVS with the 2.4 branch, or apply the following diff http://cvs.wxwindows.org/viewcvs.cgi/wxWindows/src/mac/dc.cpp.diff?r1=1.56.2 .11&r2=1.56.2.12 (the reason is not a cvs merge problem, but a newly defined macro and a bitwise shift op) Best, Stefan > -Original Message- > From: [EMAIL PROTECTED] [mailto:pgadmin-hackers- > [EMAIL PROTECTED] On Behalf Of Leon Out > Sent: Dienstag, 9. Dezember 2003 17:26 > To: [EMAIL PROTECTED] > Subject: [pgadmin-hackers] Building wxWindows on MacOS X > > Howdy. I'm new here. Nice to meet y'all. > > I'm trying to make wxWindows on my MacOS 10.3 system (as a prereq for > pgadmin), I get the following error: > > ./bk-deps g++ -c -o monodll_dc.o -Ilib/wx/include/mac-2.5 -I./include > -I./src/png -I./src/jpeg -I./src/tiff -D_FILE_OFFSET_BITS=64 > -D_LARGE_FILES -fpascal-strings -I./src/mac/morefilex > -I/Developer/Headers/FlatCarbon -D__WXMAC__ -I./include -I./src/tiff > -I./src/jpeg -I./src/png-DwxUSE_BASE=1 -DWXMAKINGDLL -O2 -Wall > -fno-common -dynamic -fPIC src/mac/dc.cpp > src/mac/dc.cpp:1282: error: parse error before `<<' token > src/mac/dc.cpp:1287: error: parse error before `short' > make: *** [monodll_dc.o] Error 1 > > I'm using wxWindows-pgAdmin3-20030831.tar.gz. Unfortunately, I don't > have enough C++ knowledge to troubleshoot this. Can anyone lend a hand? > > I'm looking forward to getting pgadmin working in OS X! > > Thanks! > > Leon > > > ---(end of broadcast)--- > TIP 5: Have you checked our extensive FAQ? > >http://www.postgresql.org/docs/faqs/FAQ.html ---(end of broadcast)--- TIP 8: explain analyze is your friend
[pgadmin-hackers] Mac OS X configuration
I recently downloaded pgadmin3 sources (from CVS) and bootstrapped and started to configure it (./configure --enable-static --enable-debug). It however stopped while checking pgsql. I checked the configure script and noticed that in LIBS "-lcrypt" is specified. This is wrong in OS X, as the needed functions exist in the system (just "#include ") and no libcrypt exists! Compiling stopped with some error, have to see what that is… ! ! Jyrki Wahlstedt ! Viialankatu 15 as 8mob. +358-40-502 0164 ! FI-32700 Huittinen ! ! Our life is no dream; but it ought to become one and perhaps will. ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
[pgadmin-hackers] Nuvver new wx Snapshot
Hi all, There is now a -9 wx snapshot available on Snake in the usual location. This adds support for Tagalog. Cheers, Dave. ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
[pgadmin-hackers] Snake/CVS downtime
---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
[pgadmin-hackers] Snake/CVS Downtime
I'll include the message this time... At 3:30PM GMT 10 Dec 2003 both snake.pgadmin.org and cvs.pgadmin.org will be shutdown whilst some electrical work is undertaken. We expect them to be available again by 5PM. Apologies for any inconvenience. Regards, Dave ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [pgadmin-hackers] Mac OS X configuration
Jyrki Wahlstedt wrote: I recently downloaded pgadmin3 sources (from CVS) and bootstrapped and started to configure it (./configure --enable-static --enable-debug). It however stopped while checking pgsql. I checked the configure script and noticed that in LIBS "-lcrypt" is specified. This is wrong in OS X, as the needed functions exist in the system (just "#include ") and no libcrypt exists! Compiling stopped with some error, have to see what that is… Have you looked at the wxMac wiki: http://wiki.wxwindows.org/wiki.pl?Installing_WxMac ahp ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[pgadmin-hackers] Solaris port status
Hi all, As I hoped in my previous mail, I finally got it running! Congratulation for your code and a big thank to Adam's "configure" scripts! It was quite straight to get it build although I had to patch one file in pgAdmin3 (see patch attached). 1) The patch attached just add a define concerning INADDR_NONE which is not defined in solaris headers. I think the patch places the 3 lines where they should be but please correct it if it doesn't suite your taste :) 2) All the build were done with gcc 3.3.2 3) I observed "strange" behaviours (wx asserts and things like this) but I was able to connect to a db and to view tables and data in them :). I must say that the wxWin I used was rapidly patched with some failed hunks... I did not want to take too much time with wx as Andreas knows it better than me. So, would it be possible for us to move to the snapshot I used for this build (http://wxwindows.sourceforge.net/snapshots/wx-cvs-20031207.tar.bz2) ? Andreas, can you take some time for this ? Is there any chance to get a Solaris box which could host the build ? For the moment, the only thing I could get by broadcasting to my friend is a "SS 5" which I doubt I can install sol 9 on it. I'm waiting for another answer but if you know someone who could provide better, it would be great. Regards, Raphaël Raphaël Enrici wrote: Andreas Pflug wrote: Dave Page wrote: There is a new wxWindows tarball on Snake: http://snake.pgadmin.org/snapshots/wxwindows/wxWindows-pgAdmin3-20031010 -8.tar.bz2 [ I didn't build it for debian at the moment... I was working on Solaris port. ] This version includes Andreas' recent patch to fix the crashing HTML Help under GTK bug. I had some feedback from wx about this. This problem is corrected in wx cvs head, thus as soon as we upgrade our snapshot we don't need my fix any more. At the moment, I don't see a reason why we should upgrade (Maybe the upcoming solaris port will need this? How is the status?) Hi Andreas, Dave this time it's my turn to sorry to be late :) so here it is: I succeeded only today in building wxwin on solaris here are the requirements and the configure line as a reminder for me and other helpers: The products I used as prereq are these, I compiled them from scratch although some of them may already be in Solaris 9 (listed by build order, all were configured with default ./configure --prefix=): tiff-v3.5.7.tar.gz pkgconfig-0.15.0.tar.gz glib-2.2.3.tar.gz pango-1.2.5.tar.gz atk-1.2.4.tar.bz2 jpegsrc.v6b.tar.gz libpng-1.2.5.tar gtk+-2.2.4.tar.bz2 Here is the trick for wxWindows as of 20031207 cvs snapshot (http://wxwindows.sourceforge.net/snapshots/wx-cvs-20031207.tar.bz2) : .../wxWindows-20031207/configure --enable-permissive --prefix=whatuprefer --disable-largefile --with-gtk --enable-gtk2 --enable-unicode --enable-debug --disable-shared --disable-dialupman I had to disable dialupman because it was giving a cast build error between a wxString and (char *) on line 719 [strstr arg #1] on dialup.c. Hope it's not a requisite for pgAdmin3 build...If it is one, I'll try to overlook how to bypass the problem. I'm not sure the --enable-permissive is really needed but in doubt we will keep it for the moment... I'll try a build of pgA3 until the end of the week or the beginning of next week. Do I need to port actual wx patches to get pgA3 to build... If I remember well it's an obligation concerning some pieces of the "notebook" or something like that. Another thing, I hope people can wait a bit concerning debian wx snapshots (it should be ready until the end of the week), I'd prefer to concentrate my efforts on solaris port actually. Regards, Raphaël *MULE_INTERNAL* ;p ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED]) --- src/db/pgConn.cpp.orig Wed Dec 3 13:28:54 2003 +++ src/db/pgConn.cpp Tue Dec 9 23:05:23 2003 @@ -24,6 +24,10 @@ #include #include #include + // Solaris does not define INADDR_NONE in its includes +#ifndef INADDR_NONE +#define INADDR_NONE (-1) +#endif #endif // App headers ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [pgadmin-hackers] Solaris port status
Raphaël Enrici wrote: As I hoped in my previous mail, I finally got it running! Congratulation for your code and a big thank to Adam's "configure" scripts! It was quite straight to get it build although I had to patch one file in pgAdmin3 (see patch attached). That's good news! 1) The patch attached just add a define concerning INADDR_NONE which is not defined in solaris headers. Will go to cvs as soon as the dev servers are up again. 3) I observed "strange" behaviours (wx asserts and things like this) but I was able to connect to a db and to view tables and data in them :). I must say that the wxWin I used was rapidly patched with some failed hunks... I did not want to take too much time with wx as Andreas knows it better than me. While wxAsserts will be silent when wx is compiled without debugging, we should track these down. So, would it be possible for us to move to the snapshot I used for this build (http://wxwindows.sourceforge.net/snapshots/wx-cvs-20031207.tar.bz2) ? Andreas, can you take some time for this ? Since we're merging quite some patches, we need to update from cvs; a snapshot makes things even more complicated. So I'll have to pick a specific date and time, hoping it will work on all machines. Regards, Andreas ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [pgadmin-hackers] Solaris port status
> -Original Message- > From: Raphaël Enrici [mailto:[EMAIL PROTECTED] > Sent: 10 December 2003 19:31 > To: Andreas Pflug; Dave Page > Cc: [EMAIL PROTECTED] > Subject: Solaris port status > > Hi all, > > As I hoped in my previous mail, I finally got it running! > Congratulation for your code and a big thank to Adam's > "configure" scripts! It was quite straight to get it build > although I had to patch one file in > pgAdmin3 (see patch attached). Well done Raphaël - I'll buy you a large beer if we meet sometime! > 1) The patch attached just add a define concerning > INADDR_NONE which is not defined in solaris headers. I think > the patch places the 3 lines where they should be but please > correct it if it doesn't suite your taste :) I'll hopefully look at this tomorrow. > Is there any chance to get a Solaris box which could host the build ? > For the moment, the only thing I could get by broadcasting to > my friend is a "SS 5" which I doubt I can install sol 9 on > it. I'm waiting for another answer but if you know someone > who could provide better, it would be great. Hmm, I don't have any Sparcs, but I did get MS Virtual PC 2004 yesterday. Slackware and FreeBSD run on it a treat - I was intending to try Solaris 8 x86 tomorrow (I don't have 9). It's not a box that could stay permanently of course, but I could do the occasional snapshot using it. Anyone else have access to a Sparc? Regards, Dave ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [pgadmin-hackers] Feature Request
Adam H. Pendleton wrote: ... I cut and paste the schema out of the schema "preview" pane, only to find that the text didn't use the windows line delimiter. It seems that the lines in the window are terminated with just a line feed character, instead of the CRLF used byWindows. Can we change this? (BTW, I am hitting a UNIX postgres server, could this have caused the behaviour?) BTW to see what I mean, cut and paste into Notepad, it doesn't hide LF's like Wordpad does. Patch for wx stc is pending. Regards, Andreas ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [pgadmin-hackers] Building wxWindows on MacOS X
Actually, the answer in my case was to add --with-libtiff --with-libpng --with-libjpeg --with-expat to my wxWindows configure. I was able to build wxWindows, stc, and xrc with no problems. pgadmin is compiling now. Leon On Dec 10, 2003, at 2:21 AM, Stefan Csomor wrote: Hi Leon I fear you are using the wrong makefile for stc. You did run ../configure from a macbuild directory of some sort now you must descend into contrib/src/stc of THIS macbuild directory, not into the toplevel contrib. HTH Stefan -Original Message- From: [EMAIL PROTECTED] [mailto:pgadmin-hackers- [EMAIL PROTECTED] On Behalf Of Leon Out Sent: Dienstag, 9. Dezember 2003 21:55 To: [EMAIL PROTECTED] Subject: Re: [pgadmin-hackers] Building wxWindows on MacOS X Thanks, Andreas. I got the snapshot recently mentioned here (wxWindows-pgAdmin3-20031010-8). wxWindows now builds nicely. However, I can't build contrib/src/stc. Here's what happens: --- BEGIN ERROR --- g++ -dynamiclib -single_module -o ../../../lib/libwx_mac_stc-2.5.1.0.0.dylib stcdll_PlatWX.o stcdll_ScintillaWX.o stcdll_stc.o stcdll_AutoComplete.o stcdll_CallTip.o stcdll_CellBuffer.o stcdll_ContractionState.o stcdll_Document.o stcdll_DocumentAccessor.o stcdll_Editor.o stcdll_ExternalLexer.o stcdll_Indicator.o stcdll_KeyMap.o stcdll_KeyWords.o stcdll_LexAVE.o stcdll_LexAda.o stcdll_LexAsm.o stcdll_LexBaan.o stcdll_LexBullant.o stcdll_LexCPP.o stcdll_LexCSS.o stcdll_LexConf.o stcdll_LexCrontab.o stcdll_LexEiffel.o stcdll_LexEScript.o stcdll_LexFortran.o stcdll_LexHTML.o stcdll_LexLisp.o stcdll_LexLout.o stcdll_LexLua.o stcdll_LexMMIXAL.o stcdll_LexMatlab.o stcdll_LexNsis.o stcdll_LexOthers.o stcdll_LexPOV.o stcdll_LexPS.o stcdll_LexPascal.o stcdll_LexPerl.o stcdll_LexPython.o stcdll_LexRuby.o stcdll_LexSQL.o stcdll_LexScriptol.o stcdll_LexVB.o stcdll_LineMarker.o stcdll_PropSet.o stcdll_RESearch.o stcdll_ScintillaBase.o stcdll_Style.o stcdll_StyleContext.o stcdll_UniConversion.o stcdll_ViewStyle.o stcdll_WindowAccessor.o stcdll_XPM.o -framework Carbon -framework System-L../../../lib -install_name /usr/local/lib/libwx_mac_stc-2.5.1.dylib -compatibility_version 2.5.1 -current_version 2.5.1 -lwxtiff -lwxjpeg -lwxpng-lwxexpat -framework Carbon -framework System -lz -lpthread -liconv -lwx_mac_core-2.5 -lwx_base_carbon-2.5 /usr/bin/libtool: can't locate file for: -lwxtiff /usr/bin/libtool: file: -lwxtiff is not an object file (not allowed in a library) /usr/bin/libtool: can't locate file for: -lwxjpeg /usr/bin/libtool: file: -lwxjpeg is not an object file (not allowed in a library) /usr/bin/libtool: can't locate file for: -lwxpng /usr/bin/libtool: file: -lwxpng is not an object file (not allowed in a library) /usr/bin/libtool: can't locate file for: -lwxexpat /usr/bin/libtool: file: -lwxexpat is not an object file (not allowed in a library) make: *** [../../../lib/libwx_mac_stc-2.5.1.0.0.dylib] Error 1 --- END ERROR --- I'm following the unix compilation instructions, but I did build wxWindows without GTK support. I'm assuming it's not required on the Mac. Is there a more OS X-centric install document anywhere? Thanks for your help! Leon On Dec 9, 2003, at 11:34 AM, Andreas Pflug wrote: Leon Out wrote: Howdy. I'm new here. Nice to meet y'all. I'm trying to make wxWindows on my MacOS 10.3 system (as a prereq for pgadmin), I get the following error: ./bk-deps g++ -c -o monodll_dc.o -Ilib/wx/include/mac-2.5 -I./include -I./src/png -I./src/jpeg -I./src/tiff -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -fpascal-strings -I./src/mac/morefilex -I/Developer/Headers/FlatCarbon -D__WXMAC__ -I./include -I./src/tiff -I./src/jpeg -I./src/png-DwxUSE_BASE=1 -DWXMAKINGDLL -O2 -Wall -fno-common -dynamic -fPIC src/mac/dc.cpp src/mac/dc.cpp:1282: error: parse error before `<<' token src/mac/dc.cpp:1287: error: parse error before `short' make: *** [monodll_dc.o] Error 1 I'm using wxWindows-pgAdmin3-20030831.tar.gz. Unfortunately, I don't have enough C++ knowledge to troubleshoot this. Can anyone lend a hand? I'm looking forward to getting pgadmin working in OS X! This very much sounds like a leftover of a cvs conflict, marking the conflicting lines. To start, please use our latest snapshot; the one you're using is too outdated for current pgAdmin3. Regards, Andreas ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED]) ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED] ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
