Small patch for linux building

[Ivan Vucica]

Below is a patch for getting further with building PythonOgre.

Note, I've made some changes replacing references to boost 1.34 with
1.35. This attempt to repair the build has failed, miserably, so I
have manually edited the patch below to remove those changes (sorry if
I messed the patch in the process).

Main change is that pygccxml_dev and pyplusplus_dev are no longer
used; edited accordingly.

Also CEGUI incorrectly invoked 0.5.0 where it should have invoked 0.5.0b.

The build of boost 1.34 has failed but I managed to build many
modules. Ubuntu 8.04.

--
Regards,

Ivan Vučica

OBJECT Networks :: www.objectnetworks.net
Cateia Games :: www.cateia.com

Index: environment.py
===================================================================
--- environment.py (revision 633)
+++ environment.py (working copy)
@@ -292,7 +292,7 @@
]
if isLinux() or isMac() :
buildCmds = [
- [0,"python setup.py install --prefix="+ PREFIX ,
os.path.join (os.getcwd(), base, "pygccxml_dev") ],
+ [0,"python setup.py install --prefix="+ PREFIX ,
os.path.join (os.getcwd(), base, "") ],
]
if isWindows():
buildCmds = [
@@ -314,7 +314,7 @@
]
if isLinux() or isMac() :
buildCmds = [
- [0,"python setup.py install --prefix=" + PREFIX ,
os.path.join (os.getcwd(), base, "pyplusplus_dev") ]
+ [0,"python setup.py install --prefix=" + PREFIX ,
os.path.join (os.getcwd(), base, "") ]
]
if isWindows():
buildCmds = [
@@ -824,7 +824,7 @@
]

buildCmds = [
- [0, tar + " zxf " +
os.path.join(downloadPath,base)+".tar.gz --overwrite",os.getcwd() ],
+ [0, tar + " zxf " +
os.path.join(downloadPath,"CEGUI-"+version)+".tar.gz
--overwrite",os.getcwd() ],
# [0, "patch -s -N -i ../python-ogre/patch/cegui.patch
-p0", os.path.join(os.getcwd(),base)],
[0, "echo 'EMPTY' >>./INSTALL", os.path.join(os.getcwd(),base)],
[0, "echo 'EMPTY' >>./NEWS", os.path.join(os.getcwd(),base)],

[Andy Miller]

I don't understand this patch -- pygccxml_dev etc directories do exist and you need to run python setup.py from within each..

 

What am I missing here?

Thanks

Andy

2008/7/15 Ivan Vucica <ivu...@gmail.com>:

[Tim Ansell]

<snip>

> Main change is that pygccxml_dev and pyplusplus_dev are no longer
> used; edited accordingly.
>
> Also CEGUI incorrectly invoked 0.5.0 where it should have invoked 0.5.0b.
>
> The build of boost 1.34 has failed but I managed to build many
> modules. Ubuntu 8.04.

> Index: environment.py

> ===================================================================
> --- environment.py (revision 633)
> +++ environment.py (working copy)
> @@ -292,7 +292,7 @@
> ]
> if isLinux() or isMac() :
> buildCmds = [
> - [0,"python setup.py install --prefix="+ PREFIX ,
> os.path.join (os.getcwd(), base, "pygccxml_dev") ],
> + [0,"python setup.py install --prefix="+ PREFIX ,
> os.path.join (os.getcwd(), base, "") ],
> ]

This looks like my problem. When I split pygccxml and pyplusplus it
looks like I didn't fix normal builds. I have pushed a change which
fixes this problem.

I'm not sure about the boost problems.

Tim 'Mithro' Ansell

[Tim Ansell]

Hi Andy,

Sorry this was my fault. With the deb changes I split pygccxml and
pyplusplus into two separate build targets (so I could build two
separate deb packages).

I forgot to check that they still built in non-deb mode. I have
committed the fix.

Tim 'Mithro' Ansell

On Tue, 2008-07-15 at 10:12 +0800, Andy Miller wrote:
> I don't understand this patch -- pygccxml_dev etc directories do exist
> and you need to run python setup.py from within each..
>
> What am I missing here?
>
> Thanks
> Andy

<snip>
>

[Ivan Vucica]

Hi everyone, thanks for the responses!

2008/7/15 Andy Miller <nzmi...@gmail.com>:

> I don't understand this patch -- pygccxml_dev etc directories do exist and
> you need to run python setup.py from within each..
>
> What am I missing here?
> Thanks
> Andy

Just a side note -- what may exist for you perhaps doesn't exist for
me, especially since these directories are _created_ by the scripts on
user side. A change in scripts can result in havoc when building from
clean directories.

Only way it can be tested in to rm -rf the installation directory and
follow the wiki step by step (and that's what I yesterday did for the
third or fourth time :)