Re: [pgadmin-hackers] wxWindows Build
Dave Page wrote: -Original Message- From: Andreas Pflug [mailto:[EMAIL PROTECTED] Sent: 27 June 2003 21:45 To: Dave Page Cc: Adam H. Pendleton; [EMAIL PROTECTED] Subject: Re: [pgadmin-hackers] wxWindows Build Dave Page wrote: As far as I am aware it is just the Unicode support that we use 2.5 for. Nope. The dialog metrics are vastly improved in 2.5, so gtk really looks the same as win32. Most strings won't fit in gtk if 2.4 if used, the fonts are really messed up. Still, I wonder about this version discussion. AFAIR we simply have --with-wx, and evaluate the version that's stored there. Another point of note - from the reply Raphael got from his Debian packager friend it sounds like the wx CVS is currently being turned upside-down whilst they reorganise the structure. Looks like we're stuck with 2003-06-07. We need our own version at the moment, which may be based on 2003-06-07 or 2003-06-18, and has the additional wxString patch to support that's still open. Regards, Andreas ---(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] wxWindows Build
> -Original Message- > From: Andreas Pflug [mailto:[EMAIL PROTECTED] > Sent: 27 June 2003 21:45 > To: Dave Page > Cc: Adam H. Pendleton; [EMAIL PROTECTED] > Subject: Re: [pgadmin-hackers] wxWindows Build > > > Dave Page wrote: > > > As far as I am aware it is just the Unicode support that we use 2.5 > > for. > > Nope. > > The dialog metrics are vastly improved in 2.5, so gtk really > looks the > same as win32. Most strings won't fit in gtk if 2.4 if used, > the fonts > are really messed up. > > Still, I wonder about this version discussion. AFAIR we simply have > --with-wx, and evaluate the version that's stored there. Another point of note - from the reply Raphael got from his Debian packager friend it sounds like the wx CVS is currently being turned upside-down whilst they reorganise the structure. Looks like we're stuck with 2003-06-07. Regards, Dave. ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [pgadmin-hackers] wxWindows Build
Dave Page wrote: As far as I am aware it is just the Unicode support that we use 2.5 for. Nope. The dialog metrics are vastly improved in 2.5, so gtk really looks the same as win32. Most strings won't fit in gtk if 2.4 if used, the fonts are really messed up. Still, I wonder about this version discussion. AFAIR we simply have --with-wx, and evaluate the version that's stored there. Regards, Andreas ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [pgadmin-hackers] pga3: FreeBSD Port
> -Original Message-
> From: Adam H. Pendleton [mailto:[EMAIL PROTECTED]
> Sent: 27 June 2003 17:32
> To: Dave Page
> Subject: Re: pga3: FreeBSD Port
>
>
> Dave Page wrote:
>
> >Hi All,
> >
> >First problem, FreeBSD seems to evaluate:
> >
> >if test "$pgsql_cv_libpq" == "yes" -a "$pgsql_cv_libpqfe_h" == "yes"
> >
> I didn't have this problem when I compiled pgadmin3. What
> shell are you
> using?
/bin/csh is the default in /etc/passwd, but I ran from a Konsole window
(I assume that was a csh as well). Stupidly I'm at home now and didn't
create a non-root account before I left so I can't get in to check.
> > and associated bits such that it just ran the static build test and
> >then carried on. This built successfully (yay!), however, (second
> >problem) although it statically linked the wx stuff as I wanted, it
> >dynamically linked libpq.
> >
> By dynamically linked do you mean that it added "-lpq" to the linker,
> instead of "/usr/local/pgsql/libpq.a"? It doesn't matter
> which way you
> write it, if /usr/local/pgsql/libpq.a is the only libpq.{ a | so } in
> your library path, then it will be linked against. Since
> it's a static
> library, static linking is required.
When I compiled, it dynamically linked (-lpq) despite the fact that
libpq.so was *not* in the library path and I specified --enable-static.
Both the static and dynamic libpq's are in the standard pgsql location.
I think the second 'if' failed so it just did the 'else' bit. It
obviously worked fine for the wx stuff, but that uses case not if.
if test "$pg_static_build" == "yes"
then
LIBS="$LIBS ${LIBPQ_HOME}/lib/libpq.a -lcrypt"
else
LIBS="$LIBS -lpq"
fi
I don't suppose you need braces round the var names in this case?
> >So, does this mean 'if test' is broken on FreeBSD?
> >
> Doubtful. It's more likely that my M4 is not totally portable.
>
> >Aside from those relatively minor build issues, in my 2 minute test,
> >pgAdmin 3 seems to run OK on FreeBSD 5.1!!
> >
> That's farther than I got. I ran into wxWindows include file
> problems
> when I tried to compile. Glad to hear it!
Yeah, no problems here. Fired it up, selected a language, connected to a
DB and had a brief browse around :-)
Regards, 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] pga3: FreeBSD Port
Hi All,
I just got KDE vaguely running on FreeBSD 5.1 and started working on a
port of pga3.
First problem, FreeBSD seems to evaluate:
if test "$pgsql_cv_libpq" == "yes" -a "$pgsql_cv_libpqfe_h" == "yes"
to false, even if both variables do actually equal yes. Please see
attached logfile.
As a test, I commented out the if statement:
#if test "$pgsql_cv_libpq" == "yes" -a "$pgsql_cv_libpqfe_h" ==
"yes"
#then
AC_MSG_CHECKING(pgsql in ${LIBPQ_HOME})
AC_MSG_RESULT(ok)
if test "$pg_static_build" == "yes"
then
LIBS="$LIBS ${LIBPQ_HOME}/lib/libpq.a -lcrypt"
else
LIBS="$LIBS -lpq"
fi
#else
#AC_MSG_CHECKING(pgsql in ${LIBPQ_HOME})
#AC_MSG_RESULT(failed)
#LDFLAGS="$PGSQL_OLD_LDFLAGS"
#CPPFLAGS="$PGSQL_OLD_CPPFLAGS"
#AC_MSG_ERROR([you must specify a valid pgsql installation with
--with-pgsql=DIR])
#fi
fi
])
and associated bits such that it just ran the static build test and
then carried on. This built successfully (yay!), however, (second
problem) although it statically linked the wx stuff as I wanted, it
dynamically linked libpq.
So, does this mean 'if test' is broken on FreeBSD?
Aside from those relatively minor build issues, in my 2 minute test,
pgAdmin 3 seems to run OK on FreeBSD 5.1!!
Regards, Dave
config.log
Description: config.log
---(end of broadcast)---
TIP 8: explain analyze is your friend
Re: [pgadmin-hackers] pgAdmin3 feedback
> -Original Message- > From: Jochem van Dieten [mailto:[EMAIL PROTECTED] > Sent: 27 June 2003 12:44 > To: [EMAIL PROTECTED] > Subject: Re: [pgadmin-hackers] pgAdmin3 feedback > > > Dave Page wrote: > >From: Jochem van Dieten [mailto:[EMAIL PROTECTED] > >> > >>Is the todo list public (so I don't duplicate requests)? > > > > Missed this bit - yes it is, it's here > > http://cvs.pgadmin.org/cgi-bin/viewcvs.cgi/pgadmin3/ > > Some more feature requests (currently running > pgadmin3-20030626-Win32): > - refresh button in the "View data" window Sounds reasonable. I'll add it to the todo. > - SSL support OK, should be there on the next Slackware builds. Jean-Michel, Andreas - can you enable ssl on your builds please? > - telepathy plugin Mark was working on that. As I can't sense how he's getting on, I'll assume the dev code has some bugs. > - sort users alphabetically in tree view Done (and groups). 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] pgAdmin3 feedback
Dave Page wrote: From: Jochem van Dieten [mailto:[EMAIL PROTECTED] Is the todo list public (so I don't duplicate requests)? Missed this bit - yes it is, it's here http://cvs.pgadmin.org/cgi-bin/viewcvs.cgi/pgadmin3/ Some more feature requests (currently running pgadmin3-20030626-Win32): - refresh button in the "View data" window - SSL support - telepathy plugin - sort users alphabetically in tree view Jochem ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [pgadmin-hackers] frmQueryBuilder.cpp.patch
Thanks, patch applied. Regards, Dave. > -Original Message- > From: Adam H. Pendleton [mailto:[EMAIL PROTECTED] > Sent: 26 June 2003 19:24 > To: [EMAIL PROTECTED] > Subject: [pgadmin-hackers] frmQueryBuilder.cpp.patch > > > Here is a patch that fixes bug #2 in QB. I have, of course, > encountered > another fatal bug right away :-(, but at least here's another > one down. > This code actually overcomes a problem with the wxWindows > code, not our > own, per se, but until it is fixed in wx (I have notified > them of the > problem), this will have to do. > > ahp > > ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
