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

Add Travis build support for linux and NaCl #2459

Merged
merged 2 commits into from May 6, 2013

Conversation

Projects
None yet
2 participants
@sbc100
Copy link
Contributor

commented Apr 25, 2013

This branch fixes existing build errors on linux and NaCl and adds a travis config
file for continuous integration.

@sbc100

This comment has been minimized.

Copy link
Contributor Author

commented Apr 26, 2013

Did you see the "Good to merge" additions to the PR above? Seems like a travis is a great addition. Would be good to add unit tests as well as just build tests in the future.

sbc100 added some commits Apr 25, 2013

Add .travis.yml
This builds all libraries and examples in both debug
and release for Linux and NaCl platforms.

Add travis build status image to README.mdown.

Also, split the linux dependency installation into
its own script: install-deps-linux.sh
@sbc100

This comment has been minimized.

Copy link
Contributor Author

commented Apr 29, 2013

Rebased onto master since several of the warnings was already fixed in the mean time.. Please take another look.

@sbc100 sbc100 referenced this pull request May 6, 2013

Closed

Simplify CCPhysicsNode #2507

@@ -1,6 +1,8 @@
cocos2d-x
=========

[![Build Status](https://travis-ci.org/sbc100/cocos2d-x.png?branch=travis)](https://travis-ci.org/sbc100/cocos2d-x)

This comment has been minimized.

Copy link
@dumganhar

dumganhar May 6, 2013

Contributor

Do you think we should create a new branch for travis in cocos2d/cocos2d-x repo or just using master branch directly?

This comment has been minimized.

Copy link
@sbc100

sbc100 May 6, 2013

Author Contributor

I would put master here yes.

The .travis.yml is setup to build all branches, but only one can be reported in the README (unfortunately, I imagine that will change at some point).

So you will want to merge this change, then create a travis account that is linked to
cocos2d/cocos2d-x. Once it is configured you can create a CL to change this image URL to point
to cocos2d/cococs2d-x rather than sbc100/cocos2d-x.

This comment has been minimized.

Copy link
@dumganhar

dumganhar May 6, 2013

Contributor

then create a travis account that is linked to cocos2d/cocos2d-x

Do you mean I should create a account for travis and fork cocos2d/cocos2d-x?

This comment has been minimized.

Copy link
@sbc100

sbc100 May 6, 2013

Author Contributor

They way it is supposed to work (I think), is that you log into https://travis-ci.org/ with your github account, then enable building of the existing cocos2dx repo. From then on all pushes to that repo will be tested automatically.

This comment has been minimized.

Copy link
@dumganhar

dumganhar May 6, 2013

Contributor

Will all Pull Requests be tested or just be tested after it's merged?

This comment has been minimized.

Copy link
@dumganhar

dumganhar May 6, 2013

Contributor

Ok, I think i should read Travis doc first. :)

@dumganhar dumganhar merged commit 42749ed into cocos2d:master May 6, 2013

@dumganhar

This comment has been minimized.

Copy link
Contributor

commented May 6, 2013

Merged at #2517. Thanks.

@sbc100 sbc100 deleted the sbc100:travis branch May 6, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.