Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update the compilation config #21

Closed
zwetan opened this issue Dec 8, 2015 · 7 comments
Closed

update the compilation config #21

zwetan opened this issue Dec 8, 2015 · 7 comments
Milestone

Comments

@zwetan
Copy link
Member

zwetan commented Dec 8, 2015

now that we have tested all our setup
we need to push back some build config change

@zwetan
Copy link
Member Author

zwetan commented Dec 8, 2015

yes that mean in its actual state the source code will not build

@zwetan zwetan added this to the 0.4.1 milestone Jan 8, 2016
@zwetan
Copy link
Member Author

zwetan commented Jan 8, 2016

added new option build.MacOSXSDK = 109
this will force the build under Mac OS X
to use the Mac OS X SDK 10.9

the binaries generated will be compatible with

  • Mac OS X 10.9
  • Mac OS X 10.10
  • Mac OS X 10.11

but they will fail with any version of Mac OS X lower than 10.9
eg. it will not work with Mac OS X 10.8 Mountain Lion or earlier
see Supported Operating System - Mac OS X

@zwetan
Copy link
Member Author

zwetan commented Jan 8, 2016

added new option build.makejobs = 3
Allow to set the number of make jobs that can run silmutaneously
setup by default to 3 (eg. 2 cores * 1.5 = 3)

if you have more cores you can increase this
number to speed up the build

for ex: on my Mac i7 with quad core I use
build.makejobs = 5

@zwetan
Copy link
Member Author

zwetan commented Jan 8, 2016

now all builds and build targets have been updated
to be in sync in what is documented in
Developer Environment

now the build will autodetect the python executable under Windows
because stupid Java does not understand 'python' under Cygwin
we need to use 'python2.7.exe'

the build is made in such a way that even if python version is updated
it should still work, eg with 'python.3.0.exe' etc.

@zwetan
Copy link
Member Author

zwetan commented Jan 8, 2016

all builds have been run and tested under Mac OS X

@zwetan
Copy link
Member Author

zwetan commented Jan 9, 2016

all builds have been run and tested under Linux Ubuntu

@zwetan
Copy link
Member Author

zwetan commented Jan 9, 2016

all builds have been run and tested under Windows

@zwetan zwetan closed this as completed Jan 10, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant