[pgadmin-hackers] Make install of .mo and .po files in pgAdmin3
Dear all, I cannot find any language files ( .mo and .po) installed under GNU/Linux, although the required paths were added to Make.am. I miss something very simple... Could you explain me how to make install these files? Cheers, Jean-Michel ---(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] I'm Back
On Friday 20 June 2003 23:22, Dave Page wrote: > pls see the src directory on snake for a pre-bootstrapped source distro. Several packagers will be building from CVS, because we do not need to fetch the whole archive. Would it be possible to run a cron job every 2 hours to bootstrap and commit to CVS? I can do it if you whish. If no change was introduced, in the configure script and needed files, the versions will stay the same. Otherwise, the scripts will be updated. What do you think of it? Cheers, Jean-Michel ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [pgadmin-hackers] I'm Back
On Friday 20 June 2003 23:06, Dave Page wrote: > We do, it's on Snake and www.pgadmin.org. The build-snapshot script does > it by getting a clean tree, bootstrapping, configuring and then running > make dist. I run such scripts for wxGTKud and pgadmin.spec RPMs. They have several arguments like source_dirs and target_host and take care of scp uploading (which is not at stake here). I will commit them to CVS when finished. But these scripts are not really standard. "Make dist" is used by packagers of Linux vendors to ease creation of RPMs. It is the standard way. I'll submit a patch... Cheers, Jean-Michel ---(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] I'm Back
> -Original Message- > From: Jean-Michel POURE [mailto:[EMAIL PROTECTED] > Sent: 20 June 2003 17:30 > To: Andreas Pflug; Adam H. Pendleton; [EMAIL PROTECTED] > Subject: Re: [pgadmin-hackers] I'm Back > > > On Friday 20 June 2003 17:24, Andreas Pflug wrote: > > Do we need autoconf to be running on all systems? It's just for > > creating the configure scripts, and the normal "download > and compile" > > user will never use autoconf. He'll "configure; make; make install" > > and that's ok. An ambitious user who wants to contribute or > sth. will > > be required to use the latest tools, including autoconf. > > You are dammed right... I should run autoconf on my Redhat 9 > build host and > transfer the files to the Mandrake 8.2 host. Let's see if it works... > > This also means we should run autoconf latest version and > commit the files to > CVS. Any idea? pls see the src directory on snake for a pre-bootstrapped source distro. Regards, Dave. ---(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] pga2: fix and add
Hi Frank, Can I have the fixes only please - we're in beta so no new code right now. I was also going to email you to suggest a Beta 2 release. The first seems pretty good, and the sooner we get a full release out the better. I also want to avoid pga2 & pga3 releasing together. Any objections? Regards, Dave. > -Original Message- > From: frank_lupo [mailto:[EMAIL PROTECTED] > Sent: 20 June 2003 18:29 > To: Dave Page; pgadmin-hackers > Subject: pga2: fix and add > > > Hi Dave, > > I have fix and add new functionality. > > frmmain > - fix drop > - fix properties > > frmSQLOutput > - add f5 refresh > - add canc delete record > - add f2 edit rcord > - add ins add record > - add esc close edit/add record > - add f4 save record > > frmoptions > - add Show Users For Privileges > - fix form Privileges > - add Ask Delete Object Database > > frmconnect > - add description connection > > > Bye !! > Frank Lupo (Wolf) !! > > /\_ _/\ > \ o o / > --ooo-ooo--- > > -- > GPG Key: http://users.jc-hosting.co.uk/frank_lupo/files/publickey.txt > > WebSite: http://users.jc-hosting.co.uk/frank_lupo > > > -- > Email.it, the professional e-mail, gratis per te: http://www.email.it/f Sponsor: L'interpretazione dei doni di orti, frutteti, prati e giardini nel nostro Ristoro Sunflower. Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=1478&d=20-6 ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [pgadmin-hackers] CVS version does not compile
> -Original Message- > From: Andreas Pflug [mailto:[EMAIL PROTECTED] > Sent: 20 June 2003 21:51 > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED]; Dave Page; Adam Pendleton > Subject: Re: [pgadmin-hackers] CVS version does not compile > > > - Linkage has been changed again. in stead of > LIB=... -L$(WX_HOME)/lib -l wx_gtk2ud_stc -lwc -l > wx_gtk2ud_xrc which will link static or dynamic libraries as > appropriate, it now says > LIB=... -l$(WX_HOME)/lib/libwx_gtk2ud_stc.a, > tying it to the static libraries (I dont have them...) This > is done for > stc and xrc, not for the base wx lib. > > Please revert it back to the flexible solution. > That was changed because it is the correct solution. Debug builds use wx statically, and following some bug reports, I changed it to use static xrc, stc and libpq as well. Release builds are dynamic in all ways. However, I realise this is not ideal, so proposed a change earlier that will allow any combination of release/debug & static/dynamic. I believe Adam is now working on it. Regards, Dave ---(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] pgAdmin3 feature freeze?
> -Original Message- > From: Andreas Pflug [mailto:[EMAIL PROTECTED] > Sent: 20 June 2003 17:52 > To: [EMAIL PROTECTED]; Dave Page > Subject: pgAdmin3 feature freeze? > > > Exporting of data from the sql window is implemented now. > > I had a deep look at CREATE OPERATOR CLASS, and decided to to > implement > a property dialog these days. To program it in a way that's worth it, > the dialog should be really intelligent about those strategy numbers. > That's not a problem per se, but a lot of work for very few > people using > it. I believe missing this won't be a big drawback. OK, sounds good. While I think of it - one bug I noticed today but haven't been able too look at:- I have a table with a serial pkey, specified not null. I cannot add rows to it, because if I leave the column blank, the editor tries to set it to null::int4. > TODO.txt is updated accordingly. > > To give some hints about bug reporting, I added an entry to the help > menu. It uses the file src/bugreport.html. > For release, we could either remove that menu or replace it > with a real > form, that posts to the pgadmin website/mailing list. OK. So people - any more essential features? Shout now or forever hold your peace (well, until the next release anyhoo)!! Regards, Dave. ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [pgadmin-hackers] I'm Back
> -Original Message- > From: Adam H. Pendleton [mailto:[EMAIL PROTECTED] > Sent: 20 June 2003 18:27 > To: [EMAIL PROTECTED] > Cc: Andreas Pflug; [EMAIL PROTECTED] > Subject: Re: [pgadmin-hackers] I'm Back > > > Jean-Michel POURE wrote: > > > > >This also means we should run autoconf latest version and commit the > >files to > >CVS. Any idea? > > > I would prefer generating a snapshot of configure nightly, instead of > including it in CVS. Keep in mind that bootstrap also generates two > Makefile.in files, so the snapshot would have to include more > than just > 'configure'. We do, it's on Snake and www.pgadmin.org. The build-snapshot script does it by getting a clean tree, bootstrapping, configuring and then running make dist. If you need pre-bootstrapped source, grab that. Regards, Dave. ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [pgadmin-hackers] Autoconf options
Title: Message -Original Message-From: Adam H. Pendleton [mailto:[EMAIL PROTECTED] Sent: 20 June 2003 17:34To: Dave PageCc: [EMAIL PROTECTED]Subject: Re: [pgadmin-hackers] Autoconf options This would require modification of the symlink to switch between release and debug versions of wxWindows which should certainly have the same headers. I agree having multiple versions of WX is bad in general (and if you're clever enough to do it, you should be able to fix the resulting mess), but debug & release versions should be permitted imho. Okay, I will add the --with-wx-config=FILE option so that a wx-config file can be specified explicitly. This should allow side-by-side linking against debug and release. Without that option specified, release will be the default, and debug will be linked against in --enable-debug is passed. One question, what if the symlink wx-config points to a debug version of wxWindows, but they don't specify --enable-debug or --with-wx-config. We would then link against a debug version of the wx library, but release versions of stc and xrc. Do we care? No. I would say just use wx-config as we do now in all cases, unless overridden by the user. Regards, Dave.
Re: [pgadmin-hackers] CVS version does not compile
Jean-Michel POURE wrote: Cheers, Jean-Michel *** if g++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/include -I/usr/lib/wx/include/gtk2ud-2.5 -D__WXDEBUG__ -D__WXGTK__ -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -I/usr/include -DDATA_DIR=\"/usr/local/pgadmin3/share/pgadmin3/\" -Wall -g -I./include/ -I -g -O2 -MT ctlSQLResult.o -MD -MP -MF ".deps/ctlSQLResult.Tpo" \ -c -o ctlSQLResult.o `test -f 'ui/ctlSQLResult.cpp' || echo './'`ui/ctlSQLResult.cpp; \ then mv -f ".deps/ctlSQLResult.Tpo" ".deps/ctlSQLResult.Po"; \ else rm -f ".deps/ctlSQLResult.Tpo"; exit 1; \ fi There are two problems: - I used "export" as a variable name, not good for gcc. - Linkage has been changed again. in stead of LIB=... -L$(WX_HOME)/lib -l wx_gtk2ud_stc -lwc -l wx_gtk2ud_xrc which will link static or dynamic libraries as appropriate, it now says LIB=... -l$(WX_HOME)/lib/libwx_gtk2ud_stc.a, tying it to the static libraries (I dont have them...) This is done for stc and xrc, not for the base wx lib. Please revert it back to the flexible solution. Regards, Andreas ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[pgadmin-hackers] CVS version does not compile
Cheers, Jean-Michel *** if g++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/include -I/usr/lib/wx/include/gtk2ud-2.5 -D__WXDEBUG__ -D__WXGTK__ -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -I/usr/include -DDATA_DIR=\"/usr/local/pgadmin3/share/pgadmin3/\" -Wall -g -I./include/ -I -g -O2 -MT ctlSQLResult.o -MD -MP -MF ".deps/ctlSQLResult.Tpo" \ -c -o ctlSQLResult.o `test -f 'ui/ctlSQLResult.cpp' || echo './'`ui/ctlSQLResult.cpp; \ then mv -f ".deps/ctlSQLResult.Tpo" ".deps/ctlSQLResult.Po"; \ else rm -f ".deps/ctlSQLResult.Tpo"; exit 1; \ fi ui/ctlSQLResult.cpp: Dans member function « bool ctlSQLResult::Export() »: ui/ctlSQLResult.cpp:39: erreur d'analyse syntaxique avant « export » make[2]: *** [ctlSQLResult.o] Erreur 1 make[2]: Quitte le répertoire `/usr/src/redhat/BUILD/pgadmin3-0.1.1/src' make[1]: *** [all-recursive] Erreur 1 make[1]: Quitte le répertoire `/usr/src/redhat/BUILD/pgadmin3-0.1.1' make: *** [all] Erreur 2 error: Bad exit status from /var/tmp/rpm-tmp.83769 (%build) ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [pgadmin-hackers] I'm Back
On Friday 20 June 2003 19:26, Adam H. Pendleton wrote: > I would prefer generating a snapshot of configure nightly, instead of > including it in CVS. Keep in mind that bootstrap also generates two > Makefile.in files, so the snapshot would have to include more than just > 'configure'. OK, thanks. This is what I did. I only have problems finding PostgreSQL header files under SuSE and Mandrake. Also, could it be possible to support the "make distro" option? It is sometimes used to ease the making of RPMs. When make distro is run, %(date +%Y%m%d) in pgadmin.spec should be replaced with mmdd. Then, making RPMs becomes easy: rpm -tb pgadmin3.tar.bz2. I added this request to the TODO.txt file in CVS. Don't do it now, it is not urgent at all. Cheers, Jean-Michel ---(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
Re: [pgadmin-hackers] I'm Back
Jean-Michel POURE wrote: This also means we should run autoconf latest version and commit the files to CVS. Any idea? I would prefer generating a snapshot of configure nightly, instead of including it in CVS. Keep in mind that bootstrap also generates two Makefile.in files, so the snapshot would have to include more than just 'configure'. ahp ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
[pgadmin-hackers] pga2: fix and add
Hi Dave, I have fix and add new functionality. frmmain - fix drop - fix properties frmSQLOutput - add f5 refresh - add canc delete record - add f2 edit rcord - add ins add record - add esc close edit/add record - add f4 save record frmoptions - add Show Users For Privileges - fix form Privileges - add Ask Delete Object Database frmconnect - add description connection Bye !! Frank Lupo (Wolf) !! /\_ _/\ \ o o / --ooo-ooo--- -- GPG Key: http://users.jc-hosting.co.uk/frank_lupo/files/publickey.txt WebSite: http://users.jc-hosting.co.uk/frank_lupo -- Email.it, the professional e-mail, gratis per te: http://www.email.it/f Sponsor: L'interpretazione dei doni di orti, frutteti, prati e giardini nel nostro Ristoro Sunflower. Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=1478&d=20-6 pgadmin.zip Description: Zip compressed data ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [pgadmin-hackers] Autoconf options
On Friday 20 June 2003 18:02, Adam H. Pendleton wrote: > --with-pgsql-include=DIR Explicitly specify the pgsql includes directory This line is really needed for compilation under Mandrake 9.1. Otherwise, the configure script does not find libpq-fe.h. Same as for SuSE 8.2. I transfered RedHat configure script on the Mandrake host. It seems to run well apart from the --with-pgsql-include=DIR problem. Cheers, Jean-Michel ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[pgadmin-hackers] pgAdmin3 feature freeze?
Exporting of data from the sql window is implemented now. I had a deep look at CREATE OPERATOR CLASS, and decided to to implement a property dialog these days. To program it in a way that's worth it, the dialog should be really intelligent about those strategy numbers. That's not a problem per se, but a lot of work for very few people using it. I believe missing this won't be a big drawback. TODO.txt is updated accordingly. To give some hints about bug reporting, I added an entry to the help menu. It uses the file src/bugreport.html. For release, we could either remove that menu or replace it with a real form, that posts to the pgadmin website/mailing list. 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])
Re: [pgadmin-hackers] Autoconf options
Dave Page wrote:
${PGHOME}/lib will still be used to find libpq.a I assume?
Yes.
OK. Don't forget stc and xrc - that's what I had to fix this morning (it
was good pratice!) :-)
Of course. :-)
DEPRECATED:
--enable-wx-gtk2 Compiles against the gtk2 version of wxWindows
Should we deprecate this yet? How long has GTK2 been fairly standard?
Deprecated because it will automatically be detected.
--enable-wx-unicode Compiles against the unicode version of wxWindows
Yes. GTK2 should imply Unicode. I see no reason why you might want GTK2
without it.
Same situation here.
This would require modification of the symlink to switch between release
and debug versions of wxWindows which should certainly have the same
headers. I agree having multiple versions of WX is bad in general (and
if you're clever enough to do it, you should be able to fix the
resulting mess), but debug & release versions should be permitted imho.
Okay, I will add the --with-wx-config=FILE option so that a wx-config
file can be specified explicitly. This should allow side-by-side
linking against debug and release. Without that option specified,
release will be the default, and debug will be linked against in
--enable-debug is passed. One question, what if the symlink wx-config
points to a debug version of wxWindows, but they don't specify
--enable-debug or --with-wx-config. We would then link against a debug
version of the wx library, but release versions of stc and xrc. Do we
care?
ahp
Re: [pgadmin-hackers] I'm Back
On Friday 20 June 2003 17:24, Andreas Pflug wrote: > Do we need autoconf to be running on all systems? It's just for creating > the configure scripts, and the normal "download and compile" user will > never use autoconf. He'll "configure; make; make install" and that's ok. > An ambitious user who wants to contribute or sth. will be required to > use the latest tools, including autoconf. You are dammed right... I should run autoconf on my Redhat 9 build host and transfer the files to the Mandrake 8.2 host. Let's see if it works... This also means we should run autoconf latest version and commit the files to CVS. Any idea? Cheers, Jean-Michel ---(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
Re: [pgadmin-hackers] Autoconf options
Adam H. Pendleton wrote: Here is the list of options that I am going to support. If anyone has comments, changes, etc. please let me know, otherwise I will go ahead with these options: --with-wx=DIR Specifies the root directory of the wxWindows installation (--prefix=DIR passed to configure when building wxWindows). If this setting is *not* specified, then configure will search for wxWindows in /usr, /usr/local, and /usr/local/wx2. --with-pgsql=DIR Same as above, except configure searches for pgsql in /usr, /usr/local, and /usr/local/pgsql --with-pgsql-include=DIR Explicitly specify the pgsql includes directory --enable-debug Compiles a debug version of pgAdmin3. This will override CFLAGS and CXXFLAGS and pass "-g -Wall -O0" to both of them, ensuring no optimization code is used. --enable-static Compiles a static (as static as possible, that is) version of pgAdmin3. This will pass a --static and --static-glibc option to the linker, to link against libc statically (this really won't do much, but it doesn't hurt). This will also link against static version of pgsql and wxWindows. DEPRECATED: --enable-wx-gtk2 Compiles against the gtk2 version of wxWindows --enable-wx-unicode Compiles against the unicode version of wxWindows --enable-wx-release Compiles against the release version of wxWindows --with-wx-config=FILE Explicitly specify which wx-config program to use, full path not necessary COMMENTS: Here are my comments about the above options. I, personally, don't like the last four options, because they are only necessary when a user has more than one version of wxWindows on their box. I am *not* going to include them unless I hear otherwise, and here's why. If a user, or a developer, wants to compile against multiple version of wxWindows to test options, etc. (a perfectly reasonable situation), then they can compile and install wxWindows with different prefixes. So pass a different --prefix=DIR to the wxWindows configure, and then pass that directory to the pgAdmin3 configure with --with-wx=DIR, and pgAdmin3 will compile against that version. Installing two different versions of wxWindows to the same prefix is probably bad news anyway (what if there are different versions of headers for Unicode? The old versions would get overwritten). I don't think it's necessary to support different versions in the same directory structure, and I see no need to do so. Correct me if I am wrong, but otherwise the pgAdmin3 configure will automagically detect which version of wxWindows you have specified and link accordingly. I totally agree. As for creating backwards-compatible versions of the autoconf scripts, Andreas is right. There is no need to do this. You do *not* need to run 'bootstrap' to create a snapshot, you only need to run 'configure'. In truth, it's probably not necessary to even distribute bootstrap, configure.ac, Makefile.am, or acinclude.m4 in our snapshots. The only reason for doing so is to help support platforms where the configure code fails (it happens, but not very often). Distributing those files would allow a user to re-generate configure if needed. In most cases, it is not necessary. So unless 'configure' doesn't run on Mandrake or SuSE or Debian or whatever, I feel no need to produce backwards-compatible scripts. Obviously I bow to the core developers on this one, just let me know. dito. 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])
Re: [pgadmin-hackers] Autoconf options
> -Original Message-
> From: Adam H. Pendleton [mailto:[EMAIL PROTECTED]
> Sent: 20 June 2003 17:02
> To: [EMAIL PROTECTED]
> Subject: [pgadmin-hackers] Autoconf options
>
>
> Here is the list of options that I am going to support. If
> anyone has
> comments, changes, etc. please let me know, otherwise I will
> go ahead
> with these options:
>
> --with-wx=DIR Specifies the root directory of the wxWindows
> installation (--prefix=DIR passed to configure when building
> wxWindows). If this setting is *not* specified, then configure will
> search for wxWindows in /usr, /usr/local, and /usr/local/wx2.
OK.
> --with-pgsql=DIR Same as above, except configure searches
> for pgsql in
> /usr, /usr/local, and /usr/local/pgsql
OK.
> --with-pgsql-include=DIR Explicitly specify the pgsql
> includes directory
${PGHOME}/lib will still be used to find libpq.a I assume?
> --enable-debug Compiles a debug version of pgAdmin3. This will
> override CFLAGS and CXXFLAGS and pass "-g -Wall -O0" to both of them,
> ensuring no optimization code is used.
OK.
> --enable-static Compiles a static (as static as possible, that is)
> version of pgAdmin3. This will pass a --static and --static-glibc
> option to the linker, to link against libc statically (this
> really won't
> do much, but it doesn't hurt). This will also link against static
> version of pgsql and wxWindows.
OK. Don't forget stc and xrc - that's what I had to fix this morning (it
was good pratice!) :-)
>
> DEPRECATED:
>
> --enable-wx-gtk2 Compiles against the gtk2 version of wxWindows
Should we deprecate this yet? How long has GTK2 been fairly standard?
> --enable-wx-unicode Compiles against the unicode version of wxWindows
Yes. GTK2 should imply Unicode. I see no reason why you might want GTK2
without it.
> --enable-wx-release Compiles against the release version of wxWindows
Yes, should be default now, with the --enable-debug implicity requiring
the debug version of wx.
> --with-wx-config=FILE Explicitly specify which wx-config
> program to use,
> full path not necessary
See below.
>
> COMMENTS:
>
> Here are my comments about the above options. I, personally,
> don't like
> the last four options, because they are only necessary when a
> user has
> more than one version of wxWindows on their box. I am *not* going to
> include them unless I hear otherwise, and here's why. If a
> user, or a
> developer, wants to compile against multiple version of wxWindows to
> test options, etc. (a perfectly reasonable situation), then they can
> compile and install wxWindows with different prefixes. So pass a
> different --prefix=DIR to the wxWindows configure, and then pass that
> directory to the pgAdmin3 configure with --with-wx=DIR, and pgAdmin3
> will compile against that version. Installing two different
> versions of
> wxWindows to the same prefix is probably bad news anyway
> (what if there
> are different versions of headers for Unicode? The old
> versions would
> get overwritten). I don't think it's necessary to support different
> versions in the same directory structure, and I see no need
> to do so.
> Correct me if I am wrong, but otherwise the pgAdmin3 configure will
> automagically detect which version of wxWindows you have
> specified and
> link accordingly.
This would require modification of the symlink to switch between release
and debug versions of wxWindows which should certainly have the same
headers. I agree having multiple versions of WX is bad in general (and
if you're clever enough to do it, you should be able to fix the
resulting mess), but debug & release versions should be permitted imho.
Regards, Dave.
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
Re: [pgadmin-hackers] I'm Back
Jean-Michel POURE wrote: Agreed. I may take a day or so to compile wxWindows... The Mandrake 8.2 host needs four hours to compile wxWindows... But for daily snapshots, the donated Mac is perfect. If you were living in Europe, I would send you the Mac... Even in Europe I'll bet it's still pretty expensive to ship it. :-) ahp ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
[pgadmin-hackers] Autoconf options
Here is the list of options that I am going to support. If anyone has comments, changes, etc. please let me know, otherwise I will go ahead with these options: --with-wx=DIR Specifies the root directory of the wxWindows installation (--prefix=DIR passed to configure when building wxWindows). If this setting is *not* specified, then configure will search for wxWindows in /usr, /usr/local, and /usr/local/wx2. --with-pgsql=DIR Same as above, except configure searches for pgsql in /usr, /usr/local, and /usr/local/pgsql --with-pgsql-include=DIR Explicitly specify the pgsql includes directory --enable-debug Compiles a debug version of pgAdmin3. This will override CFLAGS and CXXFLAGS and pass "-g -Wall -O0" to both of them, ensuring no optimization code is used. --enable-static Compiles a static (as static as possible, that is) version of pgAdmin3. This will pass a --static and --static-glibc option to the linker, to link against libc statically (this really won't do much, but it doesn't hurt). This will also link against static version of pgsql and wxWindows. DEPRECATED: --enable-wx-gtk2 Compiles against the gtk2 version of wxWindows --enable-wx-unicode Compiles against the unicode version of wxWindows --enable-wx-release Compiles against the release version of wxWindows --with-wx-config=FILE Explicitly specify which wx-config program to use, full path not necessary COMMENTS: Here are my comments about the above options. I, personally, don't like the last four options, because they are only necessary when a user has more than one version of wxWindows on their box. I am *not* going to include them unless I hear otherwise, and here's why. If a user, or a developer, wants to compile against multiple version of wxWindows to test options, etc. (a perfectly reasonable situation), then they can compile and install wxWindows with different prefixes. So pass a different --prefix=DIR to the wxWindows configure, and then pass that directory to the pgAdmin3 configure with --with-wx=DIR, and pgAdmin3 will compile against that version. Installing two different versions of wxWindows to the same prefix is probably bad news anyway (what if there are different versions of headers for Unicode? The old versions would get overwritten). I don't think it's necessary to support different versions in the same directory structure, and I see no need to do so. Correct me if I am wrong, but otherwise the pgAdmin3 configure will automagically detect which version of wxWindows you have specified and link accordingly. As for creating backwards-compatible versions of the autoconf scripts, Andreas is right. There is no need to do this. You do *not* need to run 'bootstrap' to create a snapshot, you only need to run 'configure'. In truth, it's probably not necessary to even distribute bootstrap, configure.ac, Makefile.am, or acinclude.m4 in our snapshots. The only reason for doing so is to help support platforms where the configure code fails (it happens, but not very often). Distributing those files would allow a user to re-generate configure if needed. In most cases, it is not necessary. So unless 'configure' doesn't run on Mandrake or SuSE or Debian or whatever, I feel no need to produce backwards-compatible scripts. Obviously I bow to the core developers on this one, just let me know. ahp ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [pgadmin-hackers] Debian Packaging
On Friday 20 June 2003 01:02, Raphaël Enrici wrote: > I've seen some mail from Jean-Michel Poure saying that pgAdmin3 must be > linked on wxwindows 2.5, so here is my question : where can I find the > exact requisites for the product so that I don't introduce some bugs > that you may have already seen/corrected ? Dear Raphaël, So you are the second French guy around... Nice to hear from you. We really appreciate your help. As Dave already answered, you can start with the unix_compilation.html page in CVS. I updated it today to remember to add a simlink, otherwise compilation will fail. Maybe you should also have a look at the wxGTK2ud.spec and pgadmin3.spec files which areat the top of the CVS root. It gives the list of the required files to install. Also, I chose the wxGTK2ud-2.5-dateoftheday for the wxGTK 2.5 packages, but you may have other naming conventions at Debian... When you are finished, how do you plan to distribute the package? Because pgAdmin3 is under heavy development, it sometimes needs a daily build to keep track of evolutions and bug fixes. Do you plan to upload daily packages to snake.pgadmin.org? Or do you plan to use Debian repositories? Also, it would be nice to describe the needed steps for compilation in snapshots.html pages in docs folder (this page was added today). Cheers, Jean-Michel ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [pgadmin-hackers] I'm Back
> The wx-config symlink should point to the most recent (that is the last
> 'make install'ed) version of wxWindows on the box. If a user has more
> than one wxWindows installation, and they want to use a version which is
> *not* symlinked (I can think of all kinds of problems with this), then
> we can provide a --with-wx-version= option so they can explicity specify
> the version they want to use (2.5-2ud, 2.4-ud, 2.4-d, etc.).
--enable-unicode = u
--with-gtk2 = gtk2
--enable-debug = d
--with-wx25=2.5
wx{gtk2 }{u}{d}{-2.5}-config
Anyway, your solution also works, so let's go for it.
> I think I can fix the scripts so that they can be used with the old
> versions of autoconf and automake. I will need you to test them to make
> sure they work, but this shouldn't be a problem.
I have a Mandrake 9.1 host home ready for testing. If you wish, just send me
your public SS key so I can give you root access. Dave already sent me his
key, but you are the ***master*** of autoconf...
> I've looked at this patch and I'm pretty sure it breaks regular pgsql
> includes on other systems, but I will create a patch that does work.
Thanks. The SuSE 8.2 host is in Germany. I will be testing your script...
> No, the Mac port is in pretty bad shape, and I don't know how much of it
> can be blamed on wxWindows (my wxWindows apps work fine on Mac). Your
> donated Mac is much too slow for me to use (slow from a network
> perspective that is), and using my laptop for development is somewhat
> tedious, though it should work for the time being. I am trying to get a
> Mac machine to put on my network here, which should speed up my Mac
> debugging.
Agreed. I may take a day or so to compile wxWindows... The Mandrake 8.2 host
needs four hours to compile wxWindows... But for daily snapshots, the donated
Mac is perfect. If you were living in Europe, I would send you the Mac...
Thanks again for your help. If we are able to release Mandrake 9.1 and SuSE
8.2 snapshots, we would certainly reach many new users.
Cheers,
Jean-Michel
---(end of broadcast)---
TIP 8: explain analyze is your friend
Re: [pgadmin-hackers] I'm Back
Adam H. Pendleton wrote: Jean-Michel POURE wrote: On Friday 20 June 2003 15:28, Adam H. Pendleton wrote: - pgAdmin3 configuration script should query wxgtk2ud-2.5-config and not wx-config symlink. The reasons is that pgAdmin3 cannot conflict with existing wxGTK 2.4 installations. Otherwise, it will never enter a Linux distribution. The wx-config symlink should point to the most recent (that is the last 'make install'ed) version of wxWindows on the box. If a user has more than one wxWindows installation, and they want to use a version which is *not* symlinked (I can think of all kinds of problems with this), then we can provide a --with-wx-version= option so they can explicity specify the version they want to use (2.5-2ud, 2.4-ud, 2.4-d, etc.). Why do we need that? There's the --with-wx option, which should point to a valid wxWindows directory, from there the version should be derived. Unicode and debug chars are derived from their appropriate options. - Mandrake 9.1 provides rather old autoconf (2.13-16mdk) and automake (1.4-21.p6.mdk) packages. No update is provided on Mandrake Cooker, the equivalent of Rawhide. Also, I tried to install these packages from source, but the installation did not pass the test. So can we do? Would it be possible to use a more complex autoconf script ... which would work on old autoconf + automake? I think I can fix the scripts so that they can be used with the old versions of autoconf and automake. I will need you to test them to make sure they work, but this shouldn't be a problem. Do we need autoconf to be running on all systems? It's just for creating the configure scripts, and the normal "download and compile" user will never use autoconf. He'll "configure; make; make install" and that's ok. An ambitious user who wants to contribute or sth. will be required to use the latest tools, including autoconf. - SuSE 8.2 installation needs a patch to find PostgreSQL headers. A patch has been sent to Dave. Please find it enclosed. Sounds strange to me. I'd expect pgsql lib and include to reside under the same directory (usr/local/include and /usr/local/lib, if no special prefix is applied). Regards, Andreas ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [pgadmin-hackers] I'm Back
> -Original Message-
> From: Adam H. Pendleton [mailto:[EMAIL PROTECTED]
> Sent: 20 June 2003 15:58
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: [pgadmin-hackers] I'm Back
>
>
> Jean-Michel POURE wrote:
>
> >On Friday 20 June 2003 15:28, Adam H. Pendleton wrote:
> >
> >
> >- pgAdmin3 configuration script should query wxgtk2ud-2.5-config and
> >not
> >wx-config symlink. The reasons is that pgAdmin3 cannot
> conflict with existing
> >wxGTK 2.4 installations. Otherwise, it will never enter a
> Linux distribution.
> >
> The wx-config symlink should point to the most recent (that
> is the last
> 'make install'ed) version of wxWindows on the box. If a user
> has more
> than one wxWindows installation, and they want to use a
> version which is
> *not* symlinked (I can think of all kinds of problems with
> this), then
> we can provide a --with-wx-version= option so they can
> explicity specify
> the version they want to use (2.5-2ud, 2.4-ud, 2.4-d, etc.).
That was my thought as well. I suggested an additional --with-wx-config
option to allow the user to specify which config file to use, no matter
what it's called.
>
> >- SuSE 8.2 installation needs a patch to find PostgreSQL headers. A
> >patch has
> >been sent to Dave. Please find it enclosed.
> >
> I've looked at this patch and I'm pretty sure it breaks regular pgsql
> includes on other systems, but I will create a patch that does work.
Agreed. I suggested a --with-pgsql-include option that overrides the
default ${PGHOME}/include. --with-pgsql would remain.
Regards, Dave.
---(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] I'm Back
Jean-Michel POURE wrote: On Friday 20 June 2003 15:28, Adam H. Pendleton wrote: - pgAdmin3 configuration script should query wxgtk2ud-2.5-config and not wx-config symlink. The reasons is that pgAdmin3 cannot conflict with existing wxGTK 2.4 installations. Otherwise, it will never enter a Linux distribution. The wx-config symlink should point to the most recent (that is the last 'make install'ed) version of wxWindows on the box. If a user has more than one wxWindows installation, and they want to use a version which is *not* symlinked (I can think of all kinds of problems with this), then we can provide a --with-wx-version= option so they can explicity specify the version they want to use (2.5-2ud, 2.4-ud, 2.4-d, etc.). - Mandrake 9.1 provides rather old autoconf (2.13-16mdk) and automake (1.4-21.p6.mdk) packages. No update is provided on Mandrake Cooker, the equivalent of Rawhide. Also, I tried to install these packages from source, but the installation did not pass the test. So can we do? Would it be possible to use a more complex autoconf script ... which would work on old autoconf + automake? I think I can fix the scripts so that they can be used with the old versions of autoconf and automake. I will need you to test them to make sure they work, but this shouldn't be a problem. - SuSE 8.2 installation needs a patch to find PostgreSQL headers. A patch has been sent to Dave. Please find it enclosed. I've looked at this patch and I'm pretty sure it breaks regular pgsql includes on other systems, but I will create a patch that does work. Your help is welcome. Do you think the wxWindows 2.5 CVS libraries are stable enough to produce a MacOsX version? This would be a killing news... No, the Mac port is in pretty bad shape, and I don't know how much of it can be blamed on wxWindows (my wxWindows apps work fine on Mac). Your donated Mac is much too slow for me to use (slow from a network perspective that is), and using my laptop for development is somewhat tedious, though it should work for the time being. I am trying to get a Mac machine to put on my network here, which should speed up my Mac debugging. ahp ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [pgadmin-hackers] I'm Back
On Friday 20 June 2003 15:28, Adam H. Pendleton wrote:
> Please send me any patches that need to
> be reviewed and I will take care of them today.
Hi Adam,
Nice to know you are back. Two weeks ago, I was sick like hell sleeping in bed
a week or so. This did not happen to me since I was a child...
My current issues are related to packaging:
- pgAdmin3 configuration script should query wxgtk2ud-2.5-config and not
wx-config symlink. The reasons is that pgAdmin3 cannot conflict with existing
wxGTK 2.4 installations. Otherwise, it will never enter a Linux distribution.
- Mandrake 9.1 provides rather old autoconf (2.13-16mdk) and automake
(1.4-21.p6.mdk) packages. No update is provided on Mandrake Cooker, the
equivalent of Rawhide. Also, I tried to install these packages from source,
but the installation did not pass the test. So can we do? Would it be
possible to use a more complex autoconf script ... which would work on old
autoconf + automake?
- SuSE 8.2 installation needs a patch to find PostgreSQL headers. A patch has
been sent to Dave. Please find it enclosed.
Your help is welcome. Do you think the wxWindows 2.5 CVS libraries are stable
enough to produce a MacOsX version? This would be a killing news...
Cheers,
Jean-Michel
? Makefile
? Makefile.in
? aclocal.m4
? autom4te.cache
? config.h
? config.h.in
? config.log
? config.status
? configure
? pgadmin3-0.1.1.tar.gz
? stamp-h1
? config/config.guess
? config/config.sub
? config/depcomp
? config/install-sh
? config/missing
? config/mkinstalldirs
? src/.deps
? src/Makefile
? src/Makefile.in
Index: Makefile.am
===
RCS file: /disk1/cvsroot/pgadmin3/Makefile.am,v
retrieving revision 1.9
diff -u -r1.9 Makefile.am
--- Makefile.am 13 Jun 2003 11:37:07 - 1.9
+++ Makefile.am 19 Jun 2003 11:25:25 -
@@ -4,7 +4,7 @@
#
# Makefile - Makefile for *nix systems
SUBDIRS = src
-EXTRA_DIST = README.txt BUGS.txt LICENCE.txt
+EXTRA_DIST = README.txt BUGS.txt LICENCE.txt pgadmin3.spec
nobase_dist_pkgdata_DATA = \
docs/en_US/pg/*.gif docs/en_US/pg/*.html docs/en_US/pg/*.css \
Index: acinclude.m4
===
RCS file: /disk1/cvsroot/pgadmin3/acinclude.m4,v
retrieving revision 1.8
diff -u -r1.8 acinclude.m4
--- acinclude.m4 4 Jun 2003 08:19:25 - 1.8
+++ acinclude.m4 19 Jun 2003 11:25:25 -
@@ -38,27 +38,27 @@
[wx_version=2.4])
])
-
-# Check for PostgreSQL library (libpq) #
-
+##
+# Check for PostgreSQL include files #
+##
AC_DEFUN([CHECK_LIBPQ],
[AC_MSG_CHECKING(for pgsql)
-AC_ARG_WITH(pgsql,
-[ --with-pgsql=DIR directory to search for pgsql libraries and headers],
+AC_ARG_WITH(pgsql-include,
+[ --with-pgsql-include=DIR directory to search for pgsql headers],
[if test "$withval" != no; then
AC_MSG_RESULT(yes)
-LIBPQ_HOME="$withval"
+LIBPQ_INCLUDE="$withval"
else
AC_MSG_RESULT(no)
fi], [
AC_MSG_RESULT(yes)
-LIBPQ_HOME=/usr/local/pgsql
-if test ! -f "${LIBPQ_HOME}/include/libpq-fe.h"
+LIBPQ_INCLUDE=/usr/local/pgsql/include
+if test ! -f "${LIBPQ_INCLUDE}/libpq-fe.h"
then
-LIBPQ_HOME=/usr/local
-if test ! -f "${LIBPQ_HOME}/include/libpq-fe.h"
+LIBPQ_INCLUDE=/usr/local/include
+if test ! -f "${LIBPQ_INCLUDE}/libpq-fe.h"
then
-LIBPQ_HOME=/usr
+LIBPQ_INCLUDE=/usr/include/pgsql
fi
fi
])
@@ -66,12 +66,11 @@
#
# Locate pgsql
#
-if test -n "${LIBPQ_HOME}"
+if test -n "${LIBPQ_INCLUDE}"
then
LIBPQ_OLD_LDFLAGS=$LDFLAGS
LIBPQ_OLD_CPPFLAGS=$CPPFLAGS
-LDFLAGS="$LDFLAGS -L${LIBPQ_HOME}/lib"
-CPPFLAGS="$CPPFLAGS -I${LIBPQ_HOME}/include"
+CPPFLAGS="$CPPFLAGS -I${LIBPQ_INCLUDE}"
LIBS="$LIBS -lssl -lcrypto"
AC_LANG_SAVE
AC_LANG_C
@@ -80,15 +79,15 @@
AC_LANG_RESTORE
if test "$pgsql_cv_libpq" = "yes" -a "$pgsql_cv_libpqfe_h" = "yes"
then
-AC_MSG_CHECKING(pgsql in ${LIBPQ_HOME})
+AC_MSG_CHECKING(pgsql)
AC_MSG_RESULT(ok)
LIBS="$LIBS -lpq"
else
-AC_MSG_CHECKING(pgsql in ${LIBPQ_HOME})
+AC_MSG_CHECKING(pgsql)
LDFLAGS="$LIBPQ_OLD_LDFLAGS"
CPPFLAGS="$LIBPQ_OLD_CPPFLAGS"
AC_MSG_RESULT(failed)
-AC_MSG_ERROR(you must specify a valid pgsql installation with --with-pgsql=DIR)
+AC_MSG_ERROR(you must specify the directory of your pgsql headers with --with-pgsql-headers=DIR)
fi
fi
])
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [pgadmin-hackers] I'm Back
Dave Page wrote: Hi Adam, Hope you're feeling better. Only a couple of things I'm aware of, and they should be in your inbox from earlier. Regards, Dave. Is it possible for them to be re-sent? I believe they got lost in the mass deleting I did when faced with 1000+ messages to read. :) ahp ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [pgadmin-hackers] I'm Back
Hi Adam, Hope you're feeling better. Only a couple of things I'm aware of, and they should be in your inbox from earlier. Regards, Dave. > -Original Message- > From: Adam H. Pendleton [mailto:[EMAIL PROTECTED] > Sent: 20 June 2003 14:29 > To: [EMAIL PROTECTED] > Subject: [pgadmin-hackers] I'm Back > > > Sorry folks, I've been battling sickeness for the past week or so, so > I've been kinda off the radar. Please send me any patches > that need to > be reviewed and I will take care of them today. Also, I've > been looking > at the Query Builder crash, and it seems to be a wxWindows bug, but I > got no love on the wxWindows list, so I may have to track it down > myself. :-( > > ahp > > > ---(end of > broadcast)--- > TIP 8: explain analyze is your friend > ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[pgadmin-hackers] I'm Back
Sorry folks, I've been battling sickeness for the past week or so, so I've been kinda off the radar. Please send me any patches that need to be reviewed and I will take care of them today. Also, I've been looking at the Query Builder crash, and it seems to be a wxWindows bug, but I got no love on the wxWindows list, so I may have to track it down myself. :-( ahp ---(end of broadcast)--- TIP 8: explain analyze is your friend
[pgadmin-hackers] po/mo files.
Hi Guys, How are we supposed to distribute the translations for pgAdmin? Just realised when adding the po files to the source build that they don't seem to be compiled or distributed with the binaries. Regards, Dave. ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [pgadmin-hackers] Snapshots downloads + patch
> -Original Message-
> From: Jean-Michel POURE [mailto:[EMAIL PROTECTED]
> Sent: 20 June 2003 10:57
> To: [EMAIL PROTECTED]
> Cc: Adam Pendleton; Dave Page
> Subject: Snapshots downloads + patch
>
>
> - SuSE 8.2
> The requested PostgreSQL header files cannot be found under
> SuSE without a patch written by Reinhard. This patch still
> needs to be reviewed. Please find it included in this email.
OK, just looked at this and it definately conflicts with changes that I
made this morning (which use ${LIBPQ_HOME} to locate libpq.a).
By the looks of it, SUSE include the extra /pgsql in the path for the
include files. Do they do the same for the libs? Perhaps we should allow
--with-pgsql-include to override the directory derived from
--with-pgsql, but leave that option there.
Adam, what do you think?
Regards, Dave.
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
Re: [pgadmin-hackers] Snapshots downloads + patch
> -Original Message- > From: Jean-Michel POURE [mailto:[EMAIL PROTECTED] > Sent: 20 June 2003 10:57 > To: [EMAIL PROTECTED] > Cc: Adam Pendleton; Dave Page > Subject: Snapshots downloads + patch > > > On Friday 20 June 2003 11:34, Dave Page wrote: > > I need to keep traffic on snake to a minimum, so if advertising > > snashots or anything, please point users to > > http://www.pgadmin.org/snapshots. This is rsync'd from snake daily. > > Dear Dave, > > This morning, I added an "Installing binary snapshots" page > (snapshot.html) to the documentation and will update the > links. This page needs more information about installing > Debian, Win32, Slackware. Yes, I saw it. Some of the closing tags looked a bit messed up btw. We should probably consider some standards for the docs as well - such as commands etc. being in italics, and html source wrapping at 80 characters. > When the page is finished, would it be possible to copy > it to http://www.pgadmin.org/snapshots/index.html? I see no reason why not. > Also, I am having problems with autoconf and automake: > > - Mandrake 91 > Old autoconf and automake versions are provided. Nothing new > on Cooker. It is impossible to update from RedHat versions. > Could you connect on the Mandrake host (I need your private > key) and try to compile pgAdmi3. Mandrake is as important as > SuSE in Germany and we need a more compliant autoconf script. Happy to help, but I cannot give you my private key as it's umm, private. My ssh2-RSA public key is below. BEGIN SSH2 PUBLIC KEY Comment: "rsa-key-20030620" B3NzaC1yc2EBJQAAAIEAiXYu7b7UBzUJHq6feNxFXpQ/oPnf5X5zzvF9 qQkhX+evQUYbXtsCHCAZ1JQmE9BRVv0Cq7/WmCQAExIgyzK8dNNByp13Cc92K+GV E5Vb4OMYksjYIPTLvd133eM8Zt0hcyU7bvc+LgGTevB34khPMcOVdsrscTEg6tpL TStrIAs= END SSH2 PUBLIC KEY > - SuSE 8.2 > The requested PostgreSQL header files cannot be found under > SuSE without a patch written by Reinhard. This patch still > needs to be reviewed. Please find it included in this email. OK, I'll take a look, but if it doesn't make sense to me I'll leave it for Adam. Regards, Dave ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[pgadmin-hackers] Snapshots downloads + patch
On Friday 20 June 2003 11:34, Dave Page wrote:
> I need to keep traffic on snake to a minimum, so if advertising snashots
> or anything, please point users to http://www.pgadmin.org/snapshots.
> This is rsync'd from snake daily.
Dear Dave,
This morning, I added an "Installing binary snapshots" page (snapshot.html)
to the documentation and will update the links. This page needs more information
about installing Debian, Win32, Slackware.
When the page is finished, would it be possible to copy
it to http://www.pgadmin.org/snapshots/index.html?
Also, I am having problems with autoconf and automake:
- Mandrake 91
Old autoconf and automake versions are provided. Nothing new on Cooker.
It is impossible to update from RedHat versions. Could you connect on the Mandrake host
(I need your private key) and try to compile pgAdmi3. Mandrake is as important as SuSE
in Germany and we need a more compliant autoconf script.
- SuSE 8.2
The requested PostgreSQL header files cannot be found under SuSE without a patch
written by Reinhard.
This patch still needs to be reviewed. Please find it included in this email.
Cheers,
Jean-Michel
? Makefile
? Makefile.in
? aclocal.m4
? autom4te.cache
? config.h
? config.h.in
? config.log
? config.status
? configure
? pgadmin3-0.1.1.tar.gz
? stamp-h1
? config/config.guess
? config/config.sub
? config/depcomp
? config/install-sh
? config/missing
? config/mkinstalldirs
? src/.deps
? src/Makefile
? src/Makefile.in
Index: Makefile.am
===
RCS file: /disk1/cvsroot/pgadmin3/Makefile.am,v
retrieving revision 1.9
diff -u -r1.9 Makefile.am
--- Makefile.am 13 Jun 2003 11:37:07 - 1.9
+++ Makefile.am 19 Jun 2003 11:25:25 -
@@ -4,7 +4,7 @@
#
# Makefile - Makefile for *nix systems
SUBDIRS = src
-EXTRA_DIST = README.txt BUGS.txt LICENCE.txt
+EXTRA_DIST = README.txt BUGS.txt LICENCE.txt pgadmin3.spec
nobase_dist_pkgdata_DATA = \
docs/en_US/pg/*.gif docs/en_US/pg/*.html docs/en_US/pg/*.css \
Index: acinclude.m4
===
RCS file: /disk1/cvsroot/pgadmin3/acinclude.m4,v
retrieving revision 1.8
diff -u -r1.8 acinclude.m4
--- acinclude.m4 4 Jun 2003 08:19:25 - 1.8
+++ acinclude.m4 19 Jun 2003 11:25:25 -
@@ -38,27 +38,27 @@
[wx_version=2.4])
])
-
-# Check for PostgreSQL library (libpq) #
-
+##
+# Check for PostgreSQL include files #
+##
AC_DEFUN([CHECK_LIBPQ],
[AC_MSG_CHECKING(for pgsql)
-AC_ARG_WITH(pgsql,
-[ --with-pgsql=DIR directory to search for pgsql libraries and headers],
+AC_ARG_WITH(pgsql-include,
+[ --with-pgsql-include=DIR directory to search for pgsql headers],
[if test "$withval" != no; then
AC_MSG_RESULT(yes)
-LIBPQ_HOME="$withval"
+LIBPQ_INCLUDE="$withval"
else
AC_MSG_RESULT(no)
fi], [
AC_MSG_RESULT(yes)
-LIBPQ_HOME=/usr/local/pgsql
-if test ! -f "${LIBPQ_HOME}/include/libpq-fe.h"
+LIBPQ_INCLUDE=/usr/local/pgsql/include
+if test ! -f "${LIBPQ_INCLUDE}/libpq-fe.h"
then
-LIBPQ_HOME=/usr/local
-if test ! -f "${LIBPQ_HOME}/include/libpq-fe.h"
+LIBPQ_INCLUDE=/usr/local/include
+if test ! -f "${LIBPQ_INCLUDE}/libpq-fe.h"
then
-LIBPQ_HOME=/usr
+LIBPQ_INCLUDE=/usr/include/pgsql
fi
fi
])
@@ -66,12 +66,11 @@
#
# Locate pgsql
#
-if test -n "${LIBPQ_HOME}"
+if test -n "${LIBPQ_INCLUDE}"
then
LIBPQ_OLD_LDFLAGS=$LDFLAGS
LIBPQ_OLD_CPPFLAGS=$CPPFLAGS
-LDFLAGS="$LDFLAGS -L${LIBPQ_HOME}/lib"
-CPPFLAGS="$CPPFLAGS -I${LIBPQ_HOME}/include"
+CPPFLAGS="$CPPFLAGS -I${LIBPQ_INCLUDE}"
LIBS="$LIBS -lssl -lcrypto"
AC_LANG_SAVE
AC_LANG_C
@@ -80,15 +79,15 @@
AC_LANG_RESTORE
if test "$pgsql_cv_libpq" = "yes" -a "$pgsql_cv_libpqfe_h" = "yes"
then
-AC_MSG_CHECKING(pgsql in ${LIBPQ_HOME})
+AC_MSG_CHECKING(pgsql)
AC_MSG_RESULT(ok)
LIBS="$LIBS -lpq"
else
-AC_MSG_CHECKING(pgsql in ${LIBPQ_HOME})
+AC_MSG_CHECKING(pgsql)
LDFLAGS="$LIBPQ_OLD_LDFLAGS"
CPPFLAGS="$LIBPQ_OLD_CPPFLAGS"
AC_MSG_RESULT(failed)
-AC_MSG_ERROR(you must specify a valid pgsql installation with --with-pgsql=DIR)
+AC_MSG_ERROR(you must specify the directory of your pgsql headers with --with-pgsql-headers=DIR)
fi
fi
])
---(end of broadcast)---
TIP 8: explain analyze is your friend
[pgadmin-hackers] Snapshots downloads
Hi Guys, I need to keep traffic on snake to a minimum, so if advertising snashots or anything, please point users to http://www.pgadmin.org/snapshots. This is rsync'd from snake daily. If you need to point a user at specific fix or whatever though, snake is fine. Cheers, Dave. ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[pgadmin-hackers] Heads Up - Dave's been screwing around with acinclude.m4!!
Just a warning really - following a couple of bug reports I've seen, I have modified acinclude.m4 such that for debug builds (ie. those for which wx-config is called with the --static option), we link with static pg, stc and xrc libs. Adam: I've make the same change on the Mac side, but am assuing that .a is the standard extension for a staic lib. Please change if necessary, or let me know and I'll do it. I would like to simplify the config options somewhat as well, comments on the following would be appreciated. 1) --enable-gtk2 should imply Unicode, hence the current unicode option should be removed. This will simplify acinclude.m4 considerably. Currently some impossible option combinations may be set. 2) Static (wrt wx and pg) builds are enabled by building with --enable-debug. Dynamic builds with --enable-release. These do not seem sensible pairings to me, so I would like to seperate them, giving us complete flexibility. Comments? BTW, I'm fairly confident I can do the work myself if no-one objects (it's easy seeing as Adam did all the hard stuff!). Regards, Dave ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [pgadmin-hackers] Debian Packaging
> -Original Message- > From: Raphaël Enrici [mailto:[EMAIL PROTECTED] > Sent: 20 June 2003 00:02 > To: [EMAIL PROTECTED] > Subject: [pgadmin-hackers] Debian Packaging > > > Hi all, > > If my question is stupid or the answer is something like read > the faq at > the url: bla, please just tell me where I can find the > information and I > will wash my eyes :) OK, get some soap! :-) Instructions for setting up a build environment are in: doc/en_US/unix_compilation.html In the pgAdmin source tree. This lists the currently recommended wx version, and all the configure options you should need. What it doesn't list is wxWindows dependencies - for those, please check the wxWindows docs. Slackware 9 for example, has everything already installed as standard. I don't know about Debian Woody... Lemme know if you get stuck :-) Regards, Dave ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
