Cxx.jl
Cxx.jl copied to clipboard
JuliaInterop
Instructions for using on CI
It would be nice if there were some good instructions on how to handle CI testing of packages that depend on Cxx.jl, particularly on Travis macOS.
I tried a simple dependency and the build stalled with Cxx.jl building clang. My current status is trying to mimic the Cxx.jl .travis.yml and seeing if one of the configurations in the matrix will work (maybe the Travis cache hacks?).
Alternatively Cxx dependencies as binaries? I.e., the clang that a Julia binary install will depend on.
Maybe I'm missing an easy way?
Cxx on Travis CI is very tricky. The .travis.yml file in this repo doesn't really work (takes too long to build Clang). I'm gonna look into putting up binaries built against the generic julia binaries, which should at least help the CI use case.
That would definitely solve my problem.
It feels kind of awkward to release a package that can't be tested on CI because of a dependency on another package in METADATA, which is why I've been holding off on AWSCxx.jl (despite it being cool and tested).
@tkelman Do you think you could run Pkg.build("Cxx") from a generic build on the linux/mac buildbots, and upload the resulting ~/.julia/v0.5/Cxx/deps somewhere for me to repackage for CI?
@tkelman Having the binaries is not just important for Travis CI but generally for all windows users. This would also close the #293 and #230. The build process of Julia with all the prerequisites and Clang on windows is really tricky - beyond the knowledge of most windows users.
Whoops, sorry I missed this over the weekend. So we can give it a shot, but the buildbots really aren't set up to do this in an automated way for packages, and I'd hate to have to do this manually every time you need to rebuild or patch or update something. I'd need to look up the github releases or bintray api's to upload the results (assuming it builds okay) somewhere convenient. And there's nothing particularly special about the Mac or Windows buildbots as compared to any person's individual machine or VM you could get off Vagrant etc. The Linux buildbots do have a fair amount of preparation done on them, but it should be mostly equivalent to a docker image such as my https://github.com/tkelman/c6g6.
master now has a .travis.yml that should be usable as a template. It's not pretty but it does work. At some point there'll be a longer term solution, but this should do for now.