Are you still using the distrib/mac/wxPythonOSX/build script to make DMG images? My "shell scripting" skills aren't really up to par, so I unfortunately am not able to understand the script completely, but I've noticed that some files are not copied over (particularly the src/common/dpycmn.cpp file and the wx/wxPython header folder). Also, it seems the OGL include files have moved into contrib, and for some reason the include folder isn't specified when building via the build script. Finally, if I copy the ogl include files into their "old" location inside include/wx, then I get a 'wxPyCheckForApp undeclared' error. If I build using the BUILD.txt instructions, none of these problems happen, so I am a bit baffled as to why there's a problem.
BTW, I am using "skiptar" as I did not build a tarball before running this.
Any idea what am I doing wrong here? Once I've successfully gotten wxMozilla building inside my "custom made" wxPythonOSX distro, I'll post the complete patch. BTW, it does look like I've successfully moved build_renamers into a config.py class, although I've only tested it from within the wx CVS so far.
Are you still using the distrib/mac/wxPythonOSX/build script to make DMG images? My "shell scripting" skills aren't really up to par, so I unfortunately am not able to understand the script completely, but I've noticed that some files are not copied over (particularly the src/common/dpycmn.cpp file and the wx/wxPython header folder). Also, it seems the OGL include files have moved into contrib, and for some reason the include folder isn't specified when building via the build script. Finally, if I copy the ogl include files into their "old" location inside include/wx, then I get a 'wxPyCheckForApp undeclared' error. If I build using the BUILD.txt instructions, none of these problems happen, so I am a bit baffled as to why there's a problem.
BTW, I am using "skiptar" as I did not build a tarball before running this.
That is probably the problem, or at least part of it. I havn't used the skiptar option in a long time. I'll take a look and see if it is worth salvaging or if it should just be removed.
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
Hi Robin,
Are you still using the distrib/mac/wxPythonOSX/build script to make DMG images? My "shell scripting" skills aren't really up to par, so I unfortunately am not able to understand the script completely, but I've noticed that some files are not copied over (particularly the src/common/dpycmn.cpp file and the wx/wxPython header folder). Also, it seems the OGL include files have moved into contrib, and for some reason the include folder isn't specified when building via the build script. Finally, if I copy the ogl include files into their "old" location inside include/wx, then I get a 'wxPyCheckForApp undeclared' error. If I build using the BUILD.txt instructions, none of these problems happen, so I am a bit baffled as to why there's a problem.
BTW, I am using "skiptar" as I did not build a tarball before running this.
That is probably the problem, or at least part of it. I havn't used the skiptar option in a long time. I'll take a look and see if it is worth salvaging or if it should just be removed.
Sorry, looks like I goofed again. I initially had problems building the tarball with makerpm, but when I went back and tried it again, it worked fine. Grrrr.... Chalk it up to figuring out how this stuff works. Although, there was one discrepency I noticed. build script expected the tarball to be in dist/$VERSION/wxPythonSrc-$VERSION.tar.gz, but on my machine it was in dist/wxPythonSrc-$VERSION.tar.gz (No directory for version). This may be what caused my initial decision to switch to building via use_cvs. Anyways, I'm now building and I'll let you know if I run into any other problems. ^_^;
Actually, I now remember why I was having problems using the tarball message. After wxWidgets finishes building and linking, I get the following output, at which point the program bombs out:
Hi Robin,
Are you still using the distrib/mac/wxPythonOSX/build script to make DMG images? My "shell scripting" skills aren't really up to par, so I unfortunately am not able to understand the script completely, but I've noticed that some files are not copied over (particularly the src/common/dpycmn.cpp file and the wx/wxPython header folder). Also, it seems the OGL include files have moved into contrib, and for some reason the include folder isn't specified when building via the build script. Finally, if I copy the ogl include files into their "old" location inside include/wx, then I get a 'wxPyCheckForApp undeclared' error. If I build using the BUILD.txt instructions, none of these problems happen, so I am a bit baffled as to why there's a problem.
BTW, I am using "skiptar" as I did not build a tarball before running this.
That is probably the problem, or at least part of it. I havn't used the skiptar option in a long time. I'll take a look and see if it is worth salvaging or if it should just be removed.
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-dev-unsubscribe@lists.wxwidgets.org
For additional commands, e-mail: wxPython-dev-help@lists.wxwidgets.org
Actually, I now remember why I was having problems using the tarball message. After wxWidgets finishes building and linking, I get the following output, at which point the program bombs out:
Thanks! Sorry to be a pain, I realize I may be one of the only other people actually trying to make a wxPython distro. ;-/
Out of curiosity, is Python a bad choice for doing things like build automation? I've been thinking about how to approach build automation for my own wxPython apps (EClass uses several 3rd party extensions that need compiled), and am not tempted by the idea of using .bat (4DOS/4NT aren't free, are they?) on Windows and learning shell scripting on Unix. I thought Python would be a good choice for this, particularly since anyone using wxPython knows the language ;-), but then again I see you don't use it for wxPython build scripts so I was wondering if there was any reason Python wouldn't be a good choice here. I did notice some problems when calling the command line, which seemed to be due to the process running as a different user (whatever user the Python app uses), but wasn't sure how easily these matters could be resolved, so I thought it might be wise to ask first. =)
Thanks,
Kevin
···
On Jun 8, 2004, at 8:39 AM, Robin Dunn wrote:
Kevin Ollivier wrote:
Hi Robin,
Actually, I now remember why I was having problems using the tarball message. After wxWidgets finishes building and linking, I get the following output, at which point the program bombs out:
~/oss/wxWidgets/wxMacCommit/wxWidgets/wxPython/_build_dmg/build/ wxPythonSrc-2.5.2.0p/include/wx ~/oss/wxWidgets/wxMacCommit/wxWidgets/wxPython/_build_dmg/build/ wxPythonSrc-2.5.2.0p/bld ~/oss/wxWidgets/wxMacCommit/wxWidgets/wxPython
ln: ./applet: File exists
ln: ./ogl: File exists
ln: ./xml: File exists
Any clues on what is going wrong here?
I'll probably be working on all the build scripts later today or tomorrow so I'll look at it then.
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-dev-unsubscribe@lists.wxwidgets.org
For additional commands, e-mail: wxPython-dev-help@lists.wxwidgets.org
Thanks! Sorry to be a pain, I realize I may be one of the only other people actually trying to make a wxPython distro. ;-/
Out of curiosity, is Python a bad choice for doing things like build automation?
Not a bad choice, I just found it to be easier to use bash/4NT when needing to run lots of external commands, do conditionals based on external command results, pipe output from one external command to another, redirectrions, etc. Also, most of these scripts started out very small and simple with just a few commands and then grew over time to the complex beasts you see now.
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
Although, there was one discrepency I noticed. build script expected the tarball to be in dist/$VERSION/wxPythonSrc-$VERSION.tar.gz, but on my machine it was in dist/wxPythonSrc-$VERSION.tar.gz (No directory for version). This may be what caused my initial decision to switch to building via use_cvs. Anyways, I'm now building and I'll let you know if I run into any other problems. ^_^;