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

list of packages needed for complete build environment #1

Open
davidjsherman opened this issue May 4, 2016 · 2 comments
Open

list of packages needed for complete build environment #1

davidjsherman opened this issue May 4, 2016 · 2 comments

Comments

@davidjsherman
Copy link

This repository sets up a build farm in Jenkins, but doesn't install the development packages that are needed to compile Aseba. Here is what I did. I don't guarantee that it is complete.

On MacOSX, I installed Homebrew and installed packages with
brew install qt qwt zzuf valgrind cmake node

On Windows, I installed MSYS2/MINGW32 and installed packages with
pacman -Sy mingw-w64-i686-{toolchain,cmake,qt4,edit rights,nodejs} git make msys2-runtime cygrunsrv mingw-w64-i686-nsis{,-nsisunz}

On Ubuntu, I used aptitude and installed packages with
aptitude add-apt-repository ppa:george-edison55/cmake-3.x
aptitude install git cmake gcc g++ qt4-dev-tools libqwt5-qt4 valgrind nodejs

I suppose this could be written down in Ansible recipes, so that setting up a build environment could be reproducible.

@stephanemagnenat
Copy link
Member

@marvelous what do you think?

@marvelous
Copy link
Collaborator

Thank you for your input!

For Ubuntu, https://github.com/aseba-community/build-server/blob/master/linux/root/srv/linux/jenkins/deb-container.sh installs the deb package build dependencies using mk-build-deps with --install. These build dependencies are declared in the control file https://github.com/aseba-community/aseba/blob/master/debian/control, please add them there. Do we need the cmake from that PPA?

For MacOSX, the setup was done by hand and lacks automation. Can you add the commands to init.sh and user.sh, depending on if they need to run as root or as an admin user?

Likewise for Windows, the setup commands go into init.ps1. Here, a lot was copied from the previous build farm.

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

3 participants