Building on the Mac seems broken

[Foster Brereton]

Hey all,

I'm looking for a little guidance here as I am interested in Polycode and would like to give it a spin. I hope this is the right place to ask such questions but the traffic seems a little low so if there is a better forum please let me know.

I am running on a Mac with Xcode 5.0.2. I have followed the directions in BUILD.md to build both the third-party dependencies as well as the polycode libraries themselves. Everything seems to be working fine up to that point, but when I try to build any of the sample applications or the IDE, I am getting a rash of problems.

In general the examples seem unable to build, with paths not set properly across the board. For example the ScreenSprites target is looking for HelloPolycodeApp.cpp in Contents/ScreenSprites/ when it should be ../../Contents/ScreenSprites. There are also basic headers (Polycode.h, PolycodeView.h) that are unable to be found because the header include paths are not set up properly.

Is this a known issue? If not I would be willing to take a stab at fixing it in the cmake files, but would need some guidance as I am not familiar with the system.

Regards,
Foster

[Ivan Safrin]

Are you building master or the screenrewrite branch?

[foster brereton]

master. Should I be on screenrewrite?

--
Foster T. Brereton ΙΧΘΥΣ Ro.3:21-26

[Foster Brereton]

I have tried building with the screenrewrite branch and am having the same errors as master.

[Ivan Safrin]

The paths should be correct, but the examples on screenrewrite are not updated for the new API changes. Your problem might be the default libc/libstdc++ setting in Xcode5. You might need to change it manually.

[foster brereton]

Respectfully, I do not think it is a problem with libc/stdlibc++. I
have posted to the forums about the same issue, as I did not know
which method was best:

http://polycode.org/forum/viewtopic.php?f=4&t=761

Within that post are links to a screencap of my Xcode build results:

http://imgur.com/Kz5ak45

As well as a pastebin of the build output:

http://pastebin.com/TUtwPeXL

Both seem to indicate a path related issue, or at least some step that
is being overlooked that should install the necessary Polycode
libraries into these paths.

[Ivan Safrin]

Hmm, did you build the "install" step in the main Polycode project?

[foster brereton]

I did not. After running the "install" step a bunch of files were
copied - so that's progress! Additionally the Polycode IDE is
compiling, however it is not linking - I suspect because the Polycode
libraries still cannot be found - are they not installed on that step?

The examples still aren't building, too - I'm assuming the paths they
are using to lookup headers is still wrong. I'll look into that some
more as well.

[Ivan Safrin]

All the paths should be setup properly if you follow the build instructions. Make sure it's not the libc/libstdc++ issues if it's a linker issue with the IDE. 

[Foster Brereton]

I believe I have followed the build instructions. The dependencies build no problem. The core libraries build no problem. The IDE and the Example files all fail to build, for various reasons mostly having to do with paths being ill-defined.

I have attached a script here - a bash script - that reproduces my steps from a clean clone of the git repository:

http://pastebin.com/U6SdRmrx

You should be able to run the script as-is at the root of the Polycode repo and - assuming we have the same setup - you should see the same errors.

I would be willing to set this up as a Travis-CI script to verify this build works as changes are made to Polycode. I set up something similar for the Adobe Source Libraries (https://travis-ci.org/stlab/adobe_source_libraries) and am somewhat comfortable with the system. Let me know.

-foster

[Foster Brereton]

I figured out what I was doing wrong with the examples. I did not realize they would be copied to the Release folder, and I was trying to build the projects while they were inside the top-level Examples folder. So those all seem to be working properly now.

I am guessing the remaining issues I am having (surrounding the IDE) have to do with the fact I haven't set up the Lua bindings, which will be the next thing I'll work on. Should that have some component(s) installed in the Release folder as well?

Thanks for taking the time to respond to my inquiries earlier. I am eager to check out the framework.

- foster