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

Linux distro cross-test results #26

Closed
jjYBdx4IL opened this issue Nov 2, 2014 · 9 comments
Closed

Linux distro cross-test results #26

jjYBdx4IL opened this issue Nov 2, 2014 · 9 comments

Comments

@jjYBdx4IL
Copy link

I have implemented simple tests that are checking whether the Libs generated on Debian Squeeze can be loaded on newer Ubuntu/Debian OSes. I'm also parsing and printing out the dynamic sections of the libraries there.

The log files (and results) have the format testlog.$project.$buildos.$testos.log and can be found there:

https://github.com/jjYBdx4IL/javacpp-presets

4 projects cannot be built because sources are not available or incomplete (flandmark depends on opencv, for example). These projects are listed in the allow_failure section of https://github.com/jjYBdx4IL/javacpp-presets/blob/develop/.travis.yml

Just FYI.

@jjYBdx4IL jjYBdx4IL changed the title Linux distro cross-tests Linux distro cross-test results Nov 2, 2014
@saudet
Copy link
Member

saudet commented Nov 3, 2014

Thanks, that's great :) I would be more interested in first knowing if we can also get Android, Mac OS X, and Windows to build though.

@jjYBdx4IL
Copy link
Author

There are cross-compilers for those systems, but in the end you will need your own Windows and Mac images to run the tests...... and better get every version of Windows and Mac release, or you likely end up with non-functioning stuff.

Another issue is with android: they have a good cross-compiler suite, but it is rather large and travis provides no caching.... lots of reason to choose the kvm way: one could provide scripts to install base images of Linux distros and for Windows and Mac one could specify manually created images (or maybe scripts too, if you have the installation media). The prepared images could then be cached somewhere locally so you don't have to initialize them for each build. Maybe I'll start a separate project for that, one that concentrates on the open stuff, but which should the provide easy hooks the insert the proprietary dependencies.

@saudet
Copy link
Member

saudet commented Nov 3, 2014

Sure, keep me updated on how that goes!

@saudet
Copy link
Member

saudet commented Nov 12, 2014

So, any news about KVM? Is it working well? Let me know! Thanks

@jjYBdx4IL
Copy link
Author

It will definitely work for Windows and Linux guests. Mac OS is potentially a problem because of license issues, hardware dongles etc...... I just have to find some spare time. :-)

@saudet
Copy link
Member

saudet commented Nov 15, 2014

Linux, Windows, that's a good start! Let me know when you have a working system. Thanks!

@saudet
Copy link
Member

saudet commented Dec 23, 2014

Hi, any news?

@saudet
Copy link
Member

saudet commented Oct 31, 2015

BTW, Docker works great. I've used it for the latest release (version 1.1). I'm guessing it would work fine on Travis CI as well!

@saudet
Copy link
Member

saudet commented Jul 30, 2017

Thanks to @vb216 we now have the builds running on Travis CI and AppVeyor for Android, Linux, Mac, and Windows, so I'm considering this issue solved. Thanks for your interest though! We still need help maintaining the system, for example, getting the samples running as tests would be a good thing to have...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants