Phoenix build - howto

Hi,

Hi,

I'm on GenToo and I'd like to build Phoenix from source.
If someone knows about a working ebuild that would be ideal,
but otherwise how to use the new build.py script.
I've tried ./build.py etg sip setup.py but etg fails :
Unable to locate Doxygen XML files ....

Assuming you have Python 2.7 (otherwise substitute the 2.7 with 3.2), try this:

python -u build.py 2.7 dox touch etg --nodoc sip build

Andrea.

"Imagination Is The Only Weapon In The War Against Reality."

# ------------------------------------------------------------- #
def ask_mailing_list_support(email):

    if mention_platform_and_version() and include_sample_app():
        send_message(email)
    else:
        install_malware()
        erase_hard_drives()
# ------------------------------------------------------------- #

···

On 30 January 2013 10:40, <jarausch> wrote:

jarausch@igpm.rwth-aachen.de wrote:

    Hi,

     > Hi,
     >
     > I'm on GenToo and I'd like to build Phoenix from source.
     > If someone knows about a working ebuild that would be ideal,
     > but otherwise how to use the new build.py script.
     > I've tried ./build.py etg sip setup.py but etg fails :
     > Unable to locate Doxygen XML files ....

    Assuming you have Python 2.7 (otherwise substitute the 2.7 with
    3.2), try this:

    python -u build.py 2.7 dox touch etg --nodoc sip build

    Andrea.

Thanks for hint. Unfortunately, build.py seems to be broken.
With
pwd = pushDir(posixjoin(wxDir(), 'docs/doxygen'))
it's looking for the docs/doxygen directory. But there is no such directory.
My docs directory contains only a "sphinx' subdirectory.

What am I missing?

wxDir() should be returning the root of the wxWidgets source tree, and it defaults to be $WXWIN from the environment or ../wxWidgets relative to the root of the Phoenix source tree. In other words, docs/doxygen is in the wxWidgets source and so you need to have it to be able to build Phoenix.

Eventually Phoenix will have a source tarball that will include all the things that are generated currently, so you will be able to build without needing to run the dox, etg, or sip commands, and will be able to use an existing wxWidgets build. But for now it needs to have the wxWidgets source tree available and to do all of the generation steps.

···

Am Mittwoch, 30. Januar 2013 21:25:22 UTC+1 schrieb Infinity77:
    On 30 January 2013 10:40, <jarausch> wrote:

--
Robin Dunn
Software Craftsman

This time with

Running command: etg
/usr/bin/python2.7 etg/_xrc.py --sip --nodoc
Traceback (most recent call last):
File “etg/_xrc.py”, line 211, in
run()
File “etg/_xrc.py”, line 124, in run
c.find(‘InsertHandler.handler’).transfer = True
File “/var/tmp/portage/dev-python/wxpython-9999/work/wxPython-src-2.9.4.0/wxPython/etgtools/extractors.py”, line 95, in find
(head, self.class.name, self.name))
etgtools.extractors.ExtractorError: Unable to find item named ‘InsertHandler’ within ClassDef named ‘wxXmlResource’
Command ‘/usr/bin/python2.7 etg/_xrc.py --sip --nodoc’ failed with exit code 1.
Finished command: etg (0m1.331s)

Thanks for another hint,

Helmut.

···

Op vrijdag 1 februari 2013 18:10:04 UTC+1 schreef Robin Dunn het volgende:

jara...@igpm.rwth-aachen.de wrote:

Am Mittwoch, 30. Januar 2013 21:25:22 UTC+1 schrieb Infinity77:

Hi,
On 30 January 2013 10:40, <jarausch> wrote:
 > Hi,
 >
 > I'm on GenToo and I'd like to build Phoenix from source.
 > If someone knows about a working ebuild that would be ideal,
 > but otherwise how to use the new build.py script.
 > I've tried ./build.py etg sip setup.py but etg fails :
 > Unable to locate Doxygen XML files ....
Assuming you have Python 2.7 (otherwise substitute the 2.7 with
3.2), try this:
python -u build.py 2.7 dox touch etg --nodoc sip build
Andrea.

Thanks for hint. Unfortunately, build.py seems to be broken.

With

pwd = pushDir(posixjoin(wxDir(), ‘docs/doxygen’))

it’s looking for the docs/doxygen directory. But there is no such directory.

My docs directory contains only a "sphinx’ subdirectory.

What am I missing?

wxDir() should be returning the root of the wxWidgets source tree, and
it defaults to be $WXWIN from the environment or …/wxWidgets relative
to the root of the Phoenix source tree. In other words, docs/doxygen is
in the wxWidgets source and so you need to have it to be able to build
Phoenix.

Eventually Phoenix will have a source tarball that will include all the
things that are generated currently, so you will be able to build
without needing to run the dox, etg, or sip commands, and will be able
to use an existing wxWidgets build. But for now it needs to have the
wxWidgets source tree available and to do all of the generation steps.

Unfortunately, building Phoenix still fails here.

jarausch@igpm.rwth-aachen.de wrote:

     >
     > Hi,
     >
     > > Hi,
     > >
     > > I'm on GenToo and I'd like to build Phoenix from source.
     > > If someone knows about a working ebuild that would be ideal,
     > > but otherwise how to use the new build.py script.
     > > I've tried ./build.py etg sip setup.py but etg fails :
     > > Unable to locate Doxygen XML files ....
     >
     > Assuming you have Python 2.7 (otherwise substitute the 2.7 with
     > 3.2), try this:
     >
     > python -u build.py 2.7 dox touch etg --nodoc sip build
     >
     > Andrea.
     >
     > Thanks for hint. Unfortunately, build.py seems to be broken.
     > With
     > pwd = pushDir(posixjoin(wxDir(), 'docs/doxygen'))
     > it's looking for the docs/doxygen directory. But there is no such
    directory.
     > My docs directory contains only a "sphinx' subdirectory.
     >
     > What am I missing?

    wxDir() should be returning the root of the wxWidgets source tree, and
    it defaults to be $WXWIN from the environment or ../wxWidgets relative
    to the root of the Phoenix source tree. In other words, docs/doxygen is
    in the wxWidgets source and so you need to have it to be able to build
    Phoenix.

    Eventually Phoenix will have a source tarball that will include all the
    things that are generated currently, so you will be able to build
    without needing to run the dox, etg, or sip commands, and will be able
    to use an existing wxWidgets build. But for now it needs to have the
    wxWidgets source tree available and to do all of the generation steps.

    Unfortunately, building Phoenix still fails here.

This time with

Running command: etg
/usr/bin/python2.7 etg/_xrc.py --sip --nodoc
Traceback (most recent call last):
File "etg/_xrc.py", line 211, in <module>
run()
File "etg/_xrc.py", line 124, in run
c.find('InsertHandler.handler').transfer = True
File
"/var/tmp/portage/dev-python/wxpython-9999/work/wxPython-src-2.9.4.0/wxPython/etgtools/extractors.py",
line 95, in find
(head, self.__class__.__name__, self.name))
etgtools.extractors.ExtractorError: Unable to find item named
'InsertHandler' within ClassDef named 'wxXmlResource'
Command '/usr/bin/python2.7 etg/_xrc.py --sip --nodoc' failed with exit
code 1.
Finished command: etg (0m1.331s)

I'm confused. Are you moving the Phoenix source into a wxPython 2.9.4.0 tree and trying to build it there? Are you using the trunk version of wxWidgets or the 2.9.4.0 version?

BTW, the Phoenix source tarball mentioned above with everything pre-generated does exist now. You can get it from the daily snapshots URL. It also includes a snapshot of wxWidgets, and you should let build.py build it too so you have matching versions. Implementing some improved install support is still a work in progress[1], but with just the build command you can get a Phoenix that can be used from the build folder without being fully installed (just set appropriate environment variables.)

[1] It's in the more-build-stuff branch in my Phoenix repo at github if anybody wants to take a look at it.

···

Op vrijdag 1 februari 2013 18:10:04 UTC+1 schreef Robin Dunn het volgende:
    jara...@igpm.rwth-aachen.de <javascript:> wrote:
     > Am Mittwoch, 30. Januar 2013 21:25:22 UTC+1 schrieb Infinity77:
     > On 30 January 2013 10:40, <jarausch> wrote:

--
Robin Dunn
Software Craftsman

Sorry, Robin, but could you give the daily snapshot URL, please.

Helmut.

···

On Friday, March 8, 2013 9:03:49 AM UTC+1, Robin Dunn wrote:

I’m confused. Are you moving the Phoenix source into a wxPython 2.9.4.0
tree and trying to build it there? Are you using the trunk version of
wxWidgets or the 2.9.4.0 version?

BTW, the Phoenix source tarball mentioned above with everything
pre-generated does exist now. You can get it from the daily snapshots
URL. It also includes a snapshot of wxWidgets, and you should let
build.py build it too so you have matching versions. Implementing some
improved install support is still a work in progress[1], but with just
the build command you can get a Phoenix that can be used from the build
folder without being fully installed (just set appropriate environment
variables.)

[1] It’s in the more-build-stuff branch in my Phoenix repo at github if
anybody wants to take a look at it.


Robin Dunn

Software Craftsman

http://wxPython.org

Hi,

···

On 18/03/2013 11:22, jarausch@igpm.rwth-aachen.de wrote:

Sorry, Robin, but could you give the daily snapshot URL, please.

http://wxpython.org/Phoenix/snapshot-builds/

Werner

Thanks a lot,

Helmut.

···

On Monday, March 18, 2013 12:06:00 PM UTC+1, werner wrote:

Hi,

On 18/03/2013 11:22, jara...@igpm.rwth-aachen.de wrote:

Sorry, Robin, but could you give the daily snapshot URL, please.

http://wxpython.org/Phoenix/snapshot-builds/

Werner