Thing with Standalone/ tree in builds needs to be documented about polycode

[ivansafrin]

Just a side note: rebuilding cmake stuff without cleaning is always a bad idea. I would recommend removing the build directory and re-running cmake every time there are significant pull updates just to be on the safe side.

Your issue has to do with the fact that you need to be using polybuild in the Standalone folder structure (I'm sorry this is completely undocumented right now!). There is a folder now called Standalone in the Polycode source tree. You need to run cmake in that folder (the usual mkdir Build, cd Build, cmake .. business) after you build and install the main Polycode project. This will create a Release/Darwin/Standalone folder and populate it with the tools as they're supposed to be packaged. Use the polybuild in the Bin folder of that structure, rather than the Framework one.

[mcclure]

"I would recommend removing the build directory and re-running cmake every time there are significant pull updates just to be on the safe side."

Would you recommend also deleting the Release/ directory in this case?

"you need to be using polybuild in the Standalone folder structure (I'm sorry this is completely undocumented right now!)."

Great, thanks, although

1. I'd still consider that a documentation bug, if nothing else; and
2. I did as you said-- I deleted all the Build folders plus Release, I built again and I built and installed Standalone. After this I ran the polybuild again, this time out of Standalone/Bin. I got the same results as before:

andis-macbook:2DPhysics_CollisionOnly mcc$ ../../../Release/Darwin/Standalone/Bin/polybuild --config=2DPhysics_CollisionOnly.xml --out=../Build/2DPhysics_CollisionOnly.polyapp
Polycode build tool v0.8.2
Reading config file from /Users/mcc/work/p/Polycode/Examples/Lua/2DPhysics_CollisionOnly/2DPhysics_CollisionOnly.xml
Reading xml from /Users/mcc/work/p/Polycode/Examples/Lua/2DPhysics_CollisionOnly/2DPhysics_CollisionOnly.xml
OK!
Entry point: 2DPhysics_CollisionOnly.lua
Width: 640
Height: 480
Anti-aliasing level: 0
Background color: 0.250000 0.250000 0.250000
Packaging 2DPhysics_CollisionOnly.lua as 2DPhysics_CollisionOnly.lua
Adding module: Physics2D
Path:/Users/mcc/work/p/Polycode/Examples/Lua/2DPhysics_CollisionOnly/../../../Release/Darwin/Standalone/Modules/Physics2D/API
Segmentation fault

...however, then things got REALLY weird!

I figured, probably I should run this in gdb so I can give Ivan a better idea of what's happening. When I ran the exact same polybuild in gdb, it completed without crashing:

andis-macbook:2DPhysics_CollisionOnly mcc$ gdb ../../../Release/Darwin/Standalone/Bin/polybuild
GNU gdb 6.3.50-20050815 (Apple version gdb-1515) (Sat Jan 15 08:33:48 UTC 2011)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "x86_64-apple-darwin"...Reading symbols for shared libraries ........ done

(gdb) run --config=2DPhysics_CollisionOnly.xml --out=../Build/2DPhysics_CollisionOnly.polyapp
Starting program: /Users/mcc/work/p/Polycode/Release/Darwin/Standalone/Bin/polybuild --config=2DPhysics_CollisionOnly.xml --out=../Build/2DPhysics_CollisionOnly.polyapp
Reading symbols for shared libraries .+++++++.................................................................................. done
Polycode build tool v0.8.2
Reading config file from /Users/mcc/work/p/Polycode/Examples/Lua/2DPhysics_CollisionOnly/2DPhysics_CollisionOnly.xml
Reading xml from /Users/mcc/work/p/Polycode/Examples/Lua/2DPhysics_CollisionOnly/2DPhysics_CollisionOnly.xml
OK!
Entry point: 2DPhysics_CollisionOnly.lua
Width: 640
Height: 480
Anti-aliasing level: 0
Background color: 0.250000 0.250000 0.250000
Packaging 2DPhysics_CollisionOnly.lua as 2DPhysics_CollisionOnly.lua
Adding module: Physics2D
Path:/Users/mcc/work/p/Polycode/Release/Darwin/Standalone/Modules/Physics2D/API
Packaging /Users/mcc/work/p/Polycode/Release/Darwin/Standalone/Modules/Physics2D/API/Physics2D/PhysicsJoint.lua as Physics2D/PhysicsJoint.lua
Packaging /Users/mcc/work/p/Polycode/Release/Darwin/Standalone/Modules/Physics2D/API/Physics2D/PhysicsScreen.lua as Physics2D/PhysicsScreen.lua
Packaging /Users/mcc/work/p/Polycode/Release/Darwin/Standalone/Modules/Physics2D/API/Physics2D/PhysicsScreenEntity.lua as Physics2D/PhysicsScreenEntity.lua
Packaging /Users/mcc/work/p/Polycode/Release/Darwin/Standalone/Modules/Physics2D/API/Physics2D/PhysicsScreenEvent.lua as Physics2D/PhysicsScreenEvent.lua
Packaging /Users/mcc/work/p/Polycode/Release/Darwin/Standalone/Modules/Physics2D/API/Physics2D.lua as Physics2D.lua
Packaging /Users/mcc/work/p/Polycode/Release/Darwin/Standalone/Modules/Physics2D/Lib/osx/Physics2D.dylib as __lib/osx/Physics2D.dylib

Program exited normally.

...and the generated polyapp was 901k (unlike the 4k ones being spit out on segfault) and actually worked totally fine.

Any idea what could be happening here? :(

EDIT: Also full disclosure I'm technically building out of tip from my bitbucket repo https://bitbucket.org/runhello/polycode/overview but, this is just top of tree from github merged with my pull request.

[mcclure]

Okay, please disregard the previous post. I massaged my build script some and now I do not get the crash any longer.

I'm going to suggest leaving this issue open until the process of using Standalone/ for polybuild is clearly documented however.

[ivansafrin]

Added the Standalone build step to build documentation.