rknegjens
commented
10 years ago Hi Dan
Thanks for your feedback. You're right that this instruction is a bit ambiguous, we will try to clarify it.
What is meant is that you should copy the default build script "build.def" (default indicated by the .def extension) to a file named "build" (with the extension removed), and then: chmod +x build; ./build
We include a default build script in this manner because the build script is likely to be different for each developer (different install paths etc.) and these changes should not be pushed to the git repo.
Please let us know if you have any further feedback
Best regards Rob
On Wed, Aug 20, 2014 at 11:14 AM, Dan Smith notifications@github.com wrote:
I'm not great with terminal scripts/building/compiling things and found your build instructions to be misleading.
"Copy shell script build.def to build, chmod +x it, and change the build path as appropriate."
I copied "build.def" to a folder "build" and got lots of errors and fiddled around with the build path for a while. Why do I need to copy the build.def file? I just executed ./build.def inside the folder I downloaded and it's worked.
For OSX, it should read:
chmod +x "build.def", then run using ./build.def.
— Reply to this email directly or view it on GitHub https://github.com/paperscape/paperscape-map-client/issues/1.
danpaulsmith
I'm not great with terminal scripts/building/compiling things and found your build instructions to be misleading.
"Copy shell script build.def to build, chmod +x it, and change the build path as appropriate."
I copied "build.def" to a folder "build" and got lots of errors and fiddled around with the build path for a while. Why do I need to copy the build.def file? I just executed ./build.def inside the folder I downloaded and it's worked.
For OSX, it should read:
chmod +x "build.def", then run using ./build.def.