Compiling from CVS status

wxPython Users
1

Hi Guys,

Can someone tell me if compiling from the current CVS is possible? I've
tried both the old and new methods but not had much success so I thought I'd
enquire so I am not wasting your time debugging something that is known to
be broken :slight_smile:

Along similar lines, is there a script available that will take a CVS image
and turn it into the image expected by the aforementioned two methods? I
found a script in there called "b" which seemed like it was intended for the
purpose and tried it last night but it didn't work (can't remember off hand
why not).

Robin, do you have any rough dates in mind as to when wxPython 2.5 will be
released? I'm just trying to plan ahead for Mahogany :slight_smile:

TIA

MarkL

2

Mark Livingstone wrote:

Hi Guys,

Can someone tell me if compiling from the current CVS is possible? I've
tried both the old and new methods but not had much success so I thought I'd
enquire so I am not wasting your time debugging something that is known to
be broken :slight_smile:

I've been building/updating CVS HEAD nearly every day for the past couple weeks, but there may be some things I havn't checked in yet. Which platform are you on? What errors do you get?

Along similar lines, is there a script available that will take a CVS image
and turn it into the image expected by the aforementioned two methods? I
found a script in there called "b" which seemed like it was intended for the
purpose and tried it last night but it didn't work (can't remember off hand
why not).

I use b during development to make a local (uninstalled) build of wxPython. The package dir will be built in the .../wxWindows/wxPython/wxPython dir and so I can test things without installing just by setting PYTHONPATH to .../wxWindows/wxPython. To use it just run "b 22" where the "22" stands for Python 2.2. It will expect to find a "python2.2" on the PATH and you need to be in the .../wxWIndows/wxPython dir when you run it.

Robin, do you have any rough dates in mind as to when wxPython 2.5 will be
released? I'm just trying to plan ahead for Mahogany :slight_smile:

Probably sometime in September, maybe first or second week. I had hoped to have the transition to SWIG 1.3 done before 2.5.0 but I need at least one big change to SWIG to make it happen and that may take a while...

路路路

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!

3

Mark Livingstone wrote:
> Hi Guys,
>
> Can someone tell me if compiling from the current CVS is possible?
I've
> tried both the old and new methods but not had much success so I
thought I'd
> enquire so I am not wasting your time debugging something that is
known to
> be broken :slight_smile:

I've been building/updating CVS HEAD nearly every day for the past
couple weeks, but there may be some things I havn't checked in yet.
Which platform are you on? What errors do you get?

A lot of my problems exist because I am just starting out with Linux and
compiling from CVS'es so I thought I'd have a go last night but neither
method was working but I honestly couldn't say what happened now. I also as
part of my QA job am building nightly wxWindows so just have to remember to
take that into account when I try to make a build with different options
for wxPython. Having a configure.cache is both a good and bad thing at times
when you are targeting wxWindows in two diferent directions. M expects a
static system and from what I see, wxPython prefers dynamic / dynamic
loading libs.

Now I know it (CVS) is fairly good, I'll pay more attention and
letyou know what probs I do have. I'm trying to build for Linux Mandrake 9.1
GTK version.

I use b during development to make a local (uninstalled)

build ofRD> wxPython. The package dir will be built in the RD>
.../wxWindows/wxPython/wxPython dir and so I can test things without RD>
installing just by setting PYTHONPATH to .../wxWindows/wxPython. ToRD> use
it just run "b 22" where the "22" stands for Python 2.2. ItwillRD> expect
to find a "python2.2" on the PATH and you need to be inthe RD>
.../wxWIndows/wxPython dir when you run it.

Got it. Will see tonight!

Probably sometime in September, maybe first or second week. I had
hoped
to have the transition to SWIG 1.3 done before 2.5.0 but I need at
least
one big change to SWIG to make it happen and that may take a while...

Vadim's off on his holidays end of this week and then Mahogany 0.65 should
go out shortly thereafter. I can't seriously start anything much before then
anyway. I'm just getting my system setup in anticipation. I'd get shot if I
suggested to anyone before 0.65 goes out to suddenly enable Python 2.2 and
2.3 detection in the configure scripts :wink:

TIA

MarkL

PS: Just in case, I also downloaded the wxPython 2.4 files today so if I
can't get something working I'm really not trying hard enough. Isn't
"unlimited downloads" in one's ISP package wonderful LOL

路路路

On Wed, 13 Aug 2003 20:55:09 -0700 Robin Dunn <robin@alldunn.com> wrote:

4

Mark Livingstone wrote:

OK. My copy of the wxWindows CVS tree is located off ~ (/home/markl). I have
the complete wxWindows and off that wxPython as at a day ago (I use the anon
CVS and it is normally a day behind :frowning:

I built wxWindows with your recommended settings except not unicode as M
doesn't yet support it. It was a debug build and all went well.

I then tried building SWIG to make sure I was on track and it worked first
time. Yay!

> Can someone tell me if compiling from the current CVS is possible?
I've
> tried both the old and new methods but not had much success so I
thought I'd
> enquire so I am not wasting your time debugging something that is
known to be broken :slight_smile:

I've been building/updating CVS HEAD nearly every day for the past
couple weeks, but there may be some things I havn't checked in yet.
Which platform are you on? What errors do you get?

OK. This time I payed more attention :slight_smile:

I use b during development to make a local (uninstalled) build of
wxPython. The package dir will be built in the
.../wxWindows/wxPython/wxPython dir and so I can test things without
installing just by setting PYTHONPATH to .../wxWindows/wxPython. To
use it just run "b 22" where the "22" stands for Python 2.2. It will
expect to find a "python2.2" on the PATH and you need to be in the
.../wxWIndows/wxPython dir when you run it.

When I do that, as root, it complains about not being able to find
wx-config. So then in setup.py I set
(WX_CONFIG="~/wxWindows/build/wx-config") and now I can start building. It
prepares CORE & GLCANVAS but if you try to build OGL, STC, XRC, GIZMOS or
DLLWIDGET you get screen after screen of parse errors, things not defined
etc. I set these to 0 in setup.py and was able to do a build install of the
rest of the options. What do I need to do to fix this up?

> Robin, do you have any rough dates in mind as to when wxPython 2.5
will be released? I'm just trying to plan ahead for Mahogany :slight_smile:

Probably sometime in September, maybe first or second week. I had
hoped
to have the transition to SWIG 1.3 done before 2.5.0 but I need at
least
one big change to SWIG to make it happen and that may take a while...

So you are working muxh to a wxWindows schedule then?! It is nice these days
only to hae a few dozen changes to the CVS each day rather than a few
hundred for wxWindows. Must be getting there nearly :wink:

TIA

MarkL

路路路

On Wed, 13 Aug 2003 20:55:09 -0700 Robin Dunn <robin@alldunn.com> wrote:

5

Mark Livingstone wrote:

> Mark Livingstone wrote:

OK. My copy of the wxWindows CVS tree is located off ~ (/home/markl). I have
the complete wxWindows and off that wxPython as at a day ago (I use the anon
CVS and it is normally a day behind :frowning:

I built wxWindows with your recommended settings except not unicode as M
doesn't yet support it. It was a debug build and all went well.

I then tried building SWIG to make sure I was on track and it worked first
time. Yay!

> > Can someone tell me if compiling from the current CVS is possible?
> I've
> > tried both the old and new methods but not had much success so I
> thought I'd
> > enquire so I am not wasting your time debugging something that is
> known to be broken :slight_smile:
>
> I've been building/updating CVS HEAD nearly every day for the past
> couple weeks, but there may be some things I havn't checked in yet.
> Which platform are you on? What errors do you get?

OK. This time I payed more attention :slight_smile:

> I use b during development to make a local (uninstalled) build of
> wxPython. The package dir will be built in the
> .../wxWindows/wxPython/wxPython dir and so I can test things without
> installing just by setting PYTHONPATH to .../wxWindows/wxPython. To
> use it just run "b 22" where the "22" stands for Python 2.2. It will
> expect to find a "python2.2" on the PATH and you need to be in the
> .../wxWIndows/wxPython dir when you run it.

When I do that, as root, it complains about not being able to find
wx-config. So then in setup.py I set
(WX_CONFIG="~/wxWindows/build/wx-config") and now I can start building.

Did you install wxWindows? If so, is the {prefix}/bin dir on your PATH?

It
prepares CORE & GLCANVAS but if you try to build OGL, STC, XRC, GIZMOS or
DLLWIDGET you get screen after screen of parse errors, things not defined
etc. I set these to 0 in setup.py and was able to do a build install of the
rest of the options. What do I need to do to fix this up?

This is a recent change in the wxPython 2.5.x build. Instead of building a copy of the contrib libs for itself it expects them to have already been built and installed as standard stanalone libs, but I still havn't updated the build instructions for this as you found out. If you cd to each of the following directories and run "make && make install" then the wxPython build will be able to find the include files and libs for the contribs.

路路路

On Wed, 13 Aug 2003 20:55:09 -0700 Robin Dunn <robin@alldunn.com> wrote:

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!

6

Mark Livingstone wrote:

> When I do that, as root, it complains about not being able to find
> wx-config. So then in setup.py I set
> (WX_CONFIG="~/wxWindows/build/wx-config") and now I can start
building.

Did you install wxWindows? If so, is the {prefix}/bin dir on your
PATH?

I did make && make install for wxWindows. What is {prefix} supposed to be set to again?

I have finally found where to put things to set them in BASH and also
discovered that when you run su, you do not have the exact same BASH
settings :frowning:

> It prepares CORE & GLCANVAS but if you try to build OGL, STC, XRC,
GIZMOS or
> DLLWIDGET you get screen after screen of parse errors, things not
defined
> etc. I set these to 0 in setup.py and was able to do a build install
>of the rest of the options. What do I need to do to fix this up?

This is a recent change in the wxPython 2.5.x build. Instead of
building a copy of the contrib libs for itself it expects them to have
already been built and installed as standard stanalone libs, but I
still havn't updated the build instructions for this as you found out.

busted :slight_smile:

cd to each of the following directories and run "make && make install"
then the wxPython build will be able to find the include files and
libs for the contribs.

Which directories?

TIA

MarkL

路路路

On Thu, 21 Aug 2003 13:16:21 -0700 Robin Dunn <robin@alldunn.com> wrote:

7

Mark Livingstone wrote:

> > When I do that, as root, it complains about not being able to find
> > wx-config. So then in setup.py I set
> > (WX_CONFIG="~/wxWindows/build/wx-config") and now I can start
> building. > > Did you install wxWindows? If so, is the {prefix}/bin dir on your
> PATH?

I did make && make install for wxWindows. What is {prefix} supposed to be set to again?

Whatever you used for the --prefix on the configure command-line, /usr/local by default.

I have finally found where to put things to set them in BASH and also
discovered that when you run su, you do not have the exact same BASH
settings :frowning:

Install sudo and configure it to allow your user ID to use it. Then you run "sudo whatever" to run whatever as root, and it inherits your current environment.

> cd to each of the following directories and run "make && make install" > then the wxPython build will be able to find the include files and
> libs for the contribs.

Which directories?

  contrib/src/gizmos
  contrib/src/ogl
  contrib/src/stc
  contrib/src/xrc

All under your build dir. I've made a little shell script in my build dir that does it for me, like this:

#!/bin/bash

make $* \
     && make -C contrib/src/gizmos $* \
     && make -C contrib/src/ogl $* \
     && make -C contrib/src/stc $* \
     && make -C contrib/src/xrc $* \

路路路

On Thu, 21 Aug 2003 13:16:21 -0700 Robin Dunn <robin@ > > > Mark Livingstone wrote:

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!