User ability to request a build from Jenkins
I still haven't persuaded cygwin to link correctly. Something horribly wrong. I've realised that the buildserver sshd is 32 bit and therefore builds a 32 bit library. I might attempt the configure sshd to run cygwin64, however it took a lot of effort to get everything to build over sshd, I'm reluctant to modify anything about sshd. I'll feel differently when I work on this tomorrow.
#1109 Modified cmake_daily to build multiple using more than one version of Visual Studio. Added (untested) mingw support.
#1109. Documentation update. daily build uses cmakeBuildAll to generate 12 Visual Studio builds.
#1109 Adding notes to explain the troubles getting CMake/MinGW/Qt 5.6 to work together.
#1109 Work in Progress on MinGW/32 daily build. With good fortune, this is now complete!
#1109 MinGW/32 daily build. Revisions following a walk-through with Sai Tallem on Skype.
#1109 CMake changes for MinGW. I have not yet succeeded in get CMake/MinGW to work.
#1109 MinGW/32 daily build. Avoid -svn-0-date builds. Changes to test suite for mingw.
#1109 Work in Progress on MinGW/32. Put stdout into binary mode for options
pC -pX, -eABC, eABC
#1109 MinGW/32 daily build. Clearingwarnings from overnight build http://exiv2.dyndns.org:8080/userContent/builds/Latest/test-svn-4546-date-2016-09-23+03-53-27.txt
#1109 MinGW/GCC should not set -std=gnu++98 because this causes 64 bit build to not link libpthreads! (on several tool chains)
Updated by Robin Mills about 6 years ago
- % Done changed from 0 to 20
I've made a good start on this and designed the UI. I've also made strong progress with #1041 (CMake/Visual Studio). I now have a script to rebuild/test exiv2 with visual studio 2005/8/10/12/13/15) in x86 and x64. This script delivers to a 'dlist' directory with all 12 builds. I'm thinking that I can use this to deliver a 'daily' and 'monthly' build of exiv2 and that might be sufficient for the purpose. I'm setting Done to 20 to reflect this progress.
Updated by Robin Mills about 6 years ago
- Target version changed from 1.0 to 0.26
- % Done changed from 20 to 80
- Estimated time changed from 50.00 h to 100.00 h
I'm going to advance this to 80% complete. The work on #1041 has taken up a lot of time (about 4 weeks). However, it's much more extensive than I anticipated. I've added a daily/weekly/monthly build to jenkins and publish the builds for user collection.
Perhaps in v0.27, I will continue to develop the UI to enable a user to precisely define the build required. However for v0.26, the work done in #1041 is a significant new service for users. The work complete does enable a user to 'request a build from jenkins'.
I'm also going to increase the estimate hours to 100. #1041 is already 100 hours. So, with both set at 100 hours and 80% complete, that does respect the 160 hours (4 weeks) that I have invested in this matter. I'm also changing the target to 0.26.
Updated by Robin Mills almost 6 years ago
- % Done changed from 80 to 90
I had a quite a lot of trouble getting all 12 MSVC builds to execute with CMake and to pass the daily_test.sh. It's been stable now for two weeks. I think CMake/Visual Studio is more-or-less complete. This has been a lot of work, however it is one of the major new features of the v0.26 release.
Updated by Robin Mills over 5 years ago
- Estimated time changed from 100.00 h to 120.00 h
In response to a discussion with Saiteja Tallam on the Forum concerning Qt/MinGW/32, I've extended the nightly build to publish those builds.
This was quite difficult for a couple of reasons:
1) It was a fight to get cmake built for MinGW/32
Although I get cmake built, it generates makefiles that fail to build the code.
I've documented the status in contrib/buildserver/cmake_daily.sh
2) I "switched horses" and perform the nightly build for MinGW using autotools
This has taken quite a serious effort to debug as the rest of the nightly build uses CMake.
Creating and testing the dist bundle is tough challenge as the build time is about 90 minutes.
The effort to perform a nightly build with autotools could be very useful in future and could be quickly used to build and test 32 bit Linux or Cygwin libraries. Or static libraries. Or special builds such as web-ready. Of course these builds could be performed with CMake. However, MinGW builds will have to be performed with Autotools until more work is undertaken to get cmake to work with MinGW.