[jira] [Commented] (XERCESC-1785) Build and test on all supported platforms
[ https://issues.apache.org/jira/browse/XERCESC-1785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16043071#comment-16043071 ] Scott Cantor commented on XERCESC-1785: --- Mac is certainly helpful, and 64-bit only is pretty much fine I think these days. I think a big advantage of the project doing *something* semi-official is to at least give people the choice to download unofficial Windows builds simply because I don't see those binaries coming back. > Build and test on all supported platforms > - > > Key: XERCESC-1785 > URL: https://issues.apache.org/jira/browse/XERCESC-1785 > Project: Xerces-C++ > Issue Type: Task > Components: Build >Reporter: Boris Kolpackov >Priority: Blocker > Fix For: 3.2.0 > > > We need to make sure that building, testing and installation work on all > platforms that we have committed to support. See the following Wiki page for > the status: > http://wiki.apache.org/xerces/XercescBuildStatus -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
[jira] [Updated] (XERCESC-2098) Add support for external continuous integration services
[ https://issues.apache.org/jira/browse/XERCESC-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Leigh updated XERCESC-2098: - Attachment: (was: 0001-samples-Makefile.am-Add-missing-continuation.patch) > Add support for external continuous integration services > > > Key: XERCESC-2098 > URL: https://issues.apache.org/jira/browse/XERCESC-2098 > Project: Xerces-C++ > Issue Type: Test > Components: Miscellaneous >Affects Versions: 3.2.0 > Environment: Unix/Linux > Windows (MSVC, Cygwin, MinGW) >Reporter: Roger Leigh > Labels: appveyor, continuous_integration, travis-ci > Attachments: > 0002-ci-Add-appveyor-support-for-Cygwin-MinGW64-and-MSVC1.patch, > 0003-ci-Add-travis-support-for-Linux.patch > > > The project does not currently have any continuous integration in place. > I've spent the last few days getting a working solution to consider. The > attached patch files add support for two commonly used services, > [Travis|https://travis-ci.org/] (Unix) and > [AppVeyor|https://www.appveyor.com] (Windows). > See this [GitHub > branch|https://github.com/rleigh-codelibre/xerces-c/commits/ci]. The last > commit has a green tick mark, which is the CI status. This links through to > the build results: > - > [Travis|https://travis-ci.org/rleigh-codelibre/xerces-c/builds/240825536?utm_source=github_status&utm_medium=notification] > - > [AppVeyor|https://ci.appveyor.com/project/rleigh-codelibre/xerces-c/build/1.0.76] > How to use this? Go to the Travis or AppVeyor websites and log in with > GitHub/BitBucket|GitLab credentials, or use you own public git repo. Enable > the service for your xerces-c git repo. Now any branch you push to your git > repo will be automatically built in several configuration combinations for > Linux (Autotools, CMake) and Windows (CMake with Cygwin, MingGW64 and MSVC > 2015). The exact combinations tested are viewable with the above build > links, or in the attached patch files. The set of test combinations can be > adjusted as desired. > This could additionally be enabled for the Apache GitHub mirror or the Apache > git repo itself, which would trigger builds for all subversion commits to do > post-commit testing. > Would there be any objection to committing these changes? -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
[jira] [Commented] (XERCESC-1785) Build and test on all supported platforms
[ https://issues.apache.org/jira/browse/XERCESC-1785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16043052#comment-16043052 ] Roger Leigh commented on XERCESC-1785: -- I can certainly look at adding MacOS X to the work linked above; it's available as a supported platform, and it would ensure that the cfurl and macosxunicodeconverter options are in the test matrix. It's currently 64-bit only; probably fine for commit testing; the matrix could be extended to 32-bits for releases if we wanted, but if we're happy with source-only releases it's probably easier to delegate that to distributions for the most part. AppVeyor does produce downloadable zips, so we could link to Windows builds if we wanted, or just let people build their own. > Build and test on all supported platforms > - > > Key: XERCESC-1785 > URL: https://issues.apache.org/jira/browse/XERCESC-1785 > Project: Xerces-C++ > Issue Type: Task > Components: Build >Reporter: Boris Kolpackov >Priority: Blocker > Fix For: 3.2.0 > > > We need to make sure that building, testing and installation work on all > platforms that we have committed to support. See the following Wiki page for > the status: > http://wiki.apache.org/xerces/XercescBuildStatus -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
RE: Adding support for continuous integration to Xerces
> I'd be very interested in any thoughts anyone had on this topic. I've > opened a ticket for it here along with an initial testable > implementation for anyone who wanted to try it out: I'm definitely going to take a look at it for my own projects since we don't have this at present for our native code libraries, but I'll definitely defer to the more long term PMC members on what, if anything, should be done on the ASF side. -- Scott
[jira] [Commented] (XERCESC-1785) Build and test on all supported platforms
[ https://issues.apache.org/jira/browse/XERCESC-1785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16043038#comment-16043038 ] Scott Cantor commented on XERCESC-1785: --- Given that this issue was created in 2008...;-) Speaking for myself, since I did the last several releases, I can only support what my project requires, which is Windows 32/64, OS X via macports, Solaris (with very minimal testing and increasingly only x86), and various usual Linuces not including Debian. >From a distribution standpoint, I abandoned the binaries entirely as I had no >way to, or time to, produce them. > Build and test on all supported platforms > - > > Key: XERCESC-1785 > URL: https://issues.apache.org/jira/browse/XERCESC-1785 > Project: Xerces-C++ > Issue Type: Task > Components: Build >Reporter: Boris Kolpackov >Priority: Blocker > Fix For: 3.2.0 > > > We need to make sure that building, testing and installation work on all > platforms that we have committed to support. See the following Wiki page for > the status: > http://wiki.apache.org/xerces/XercescBuildStatus -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
Adding support for continuous integration to Xerces
Hi folks, I'd be very interested in any thoughts anyone had on this topic. I've opened a ticket for it here along with an initial testable implementation for anyone who wanted to try it out: https://issues.apache.org/jira/browse/XERCESC-2098 On the infrastructure side, is there anyone who would be able to enable this for the Apache GitHub mirror, who has admin privileges for the GitHub mirror repository? Thanks all, Roger - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
[jira] [Commented] (XERCESC-2048) Error during build on Windows/MinGW because of LDFLAGS=-no-undefined
[ https://issues.apache.org/jira/browse/XERCESC-2048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16043033#comment-16043033 ] Roger Leigh commented on XERCESC-2048: -- The new CMake support on the trunk will allow building and testing with MinGW, e.g. https://ci.appveyor.com/project/rleigh-codelibre/xerces-c/build/1.0.76/job/4vo6enhkhday4a72 > Error during build on Windows/MinGW because of LDFLAGS=-no-undefined > - > > Key: XERCESC-2048 > URL: https://issues.apache.org/jira/browse/XERCESC-2048 > Project: Xerces-C++ > Issue Type: Bug > Components: Build >Affects Versions: 3.1.2, 3.1.3 > Environment: Windows 8.1 with MinGW >Reporter: Philip Young >Priority: Blocker > > Followed the build instructions and used ./configure LDFLAGS=-no-undefined > config.log shows the following: > Target: mingw32 > Configured with: ../gcc-4.8.1/configure --prefix=/mingw --host=mingw32 > --build=mingw32 --without-pic --enable-shared --enable-static --with-gnu-ld > --enable-lto --enable-libssp --disable-multilib > --enable-languages=c,c++,fortran,objc,obj-c++,ada --disable-sjlj-exceptions > --with-dwarf2 --disable-win32-registry --enable-libstdcxx-debug > --enable-version-specific-runtime-libs > --with-gmp=/usr/src/pkg/gmp-5.1.2-1-mingw32-src/bld > --with-mpc=/usr/src/pkg/mpc-1.0.1-1-mingw32-src/bld --with-mpfr= > --with-system-zlib --with-gnu-as --enable-decimal-float=yes --enable-libgomp > --enable-threads --with-libiconv-prefix=/mingw32 --with-libintl-prefix=/mingw > --disable-bootstrap LDFLAGS=-s CFLAGS=-D_USE_32BIT_TIME_T > Thread model: win32 > gcc version 4.8.1 (GCC) > configure:3781: $? = 0 > configure:3770: g++ -V >&5 > g++.exe: error: unrecognized command line option '-V' > g++.exe: fatal error: no input files > compilation terminated. > configure:3781: $? = 1 > configure:3770: g++ -qversion >&5 > g++.exe: error: unrecognized command line option '-qversion' > g++.exe: fatal error: no input files > compilation terminated. > configure:3781: $? = 1 > configure:3801: checking whether the C++ compiler works > configure:3823: g++ -no-undefined conftest.cpp >&5 > g++.exe: error: unrecognized command line option '-no-undefined' > configure:3827: $? = 1 > configure:3865: result: no > configure: failed program was: > | /* confdefs.h */ -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
[jira] [Commented] (XERCESC-1785) Build and test on all supported platforms
[ https://issues.apache.org/jira/browse/XERCESC-1785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16043025#comment-16043025 ] Roger Leigh commented on XERCESC-1785: -- Please see https://issues.apache.org/jira/browse/XERCESC-2098 for an attempt to automatically test on a range of common platforms. Looking at the platform list on the linked wiki page, it's quite out of date. Do we have a current list of platforms we should be supporting? > Build and test on all supported platforms > - > > Key: XERCESC-1785 > URL: https://issues.apache.org/jira/browse/XERCESC-1785 > Project: Xerces-C++ > Issue Type: Task > Components: Build >Reporter: Boris Kolpackov >Priority: Blocker > Fix For: 3.2.0 > > > We need to make sure that building, testing and installation work on all > platforms that we have committed to support. See the following Wiki page for > the status: > http://wiki.apache.org/xerces/XercescBuildStatus -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
[jira] [Updated] (XERCESC-2098) Add support for external continuous integration services
[ https://issues.apache.org/jira/browse/XERCESC-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Leigh updated XERCESC-2098: - Description: The project does not currently have any continuous integration in place. I've spent the last few days getting a working solution to consider. The attached patch files add support for two commonly used services, [Travis|https://travis-ci.org/] (Unix) and [AppVeyor|https://www.appveyor.com] (Windows). See this [GitHub branch|https://github.com/rleigh-codelibre/xerces-c/commits/ci]. The last commit has a green tick mark, which is the CI status. This links through to the build results: - [Travis|https://travis-ci.org/rleigh-codelibre/xerces-c/builds/240825536?utm_source=github_status&utm_medium=notification] - [AppVeyor|https://ci.appveyor.com/project/rleigh-codelibre/xerces-c/build/1.0.76] How to use this? Go to the Travis or AppVeyor websites and log in with GitHub/BitBucket|GitLab credentials, or use you own public git repo. Enable the service for your xerces-c git repo. Now any branch you push to your git repo will be automatically built in several configuration combinations for Linux (Autotools, CMake) and Windows (CMake with Cygwin, MingGW64 and MSVC 2015). The exact combinations tested are viewable with the above build links, or in the attached patch files. The set of test combinations can be adjusted as desired. This could additionally be enabled for the Apache GitHub mirror or the Apache git repo itself, which would trigger builds for all subversion commits to do post-commit testing. Would there be any objection to committing these changes? was: The project does not currently have any continuous integration in place. I've spent the last few days getting a working solution to consider. The attached patch files add support for two commonly used services, [Travis|https://travis-ci.org/] (Unix) and [AppVeyor|www.appveyor.com] (Windows). See this [GitHub branch|https://github.com/rleigh-codelibre/xerces-c/commits/ci]. The last commit has a green tick mark, which is the CI status. This links through to the build results: - [Travis|https://travis-ci.org/rleigh-codelibre/xerces-c/builds/240825536?utm_source=github_status&utm_medium=notification] - [AppVeyor|https://ci.appveyor.com/project/rleigh-codelibre/xerces-c/build/1.0.76] How to use this? Go to the Travis or AppVeyor websites and log in with GitHub/BitBucket|GitLab credentials, or use you own public git repo. Enable the service for your xerces-c git repo. Now any branch you push to your git repo will be automatically built in several configuration combinations for Linux (Autotools, CMake) and Windows (CMake with Cygwin, MingGW64 and MSVC 2015). The exact combinations tested are viewable with the above build links, or in the attached patch files. The set of test combinations can be adjusted as desired. This could additionally be enabled for the Apache GitHub mirror or the Apache git repo itself, which would trigger builds for all subversion commits to do post-commit testing. Would there be any objection to committing these changes? > Add support for external continuous integration services > > > Key: XERCESC-2098 > URL: https://issues.apache.org/jira/browse/XERCESC-2098 > Project: Xerces-C++ > Issue Type: Test > Components: Miscellaneous >Affects Versions: 3.2.0 > Environment: Unix/Linux > Windows (MSVC, Cygwin, MinGW) >Reporter: Roger Leigh > Labels: appveyor, continuous_integration, travis-ci > Attachments: 0001-samples-Makefile.am-Add-missing-continuation.patch, > 0002-ci-Add-appveyor-support-for-Cygwin-MinGW64-and-MSVC1.patch, > 0003-ci-Add-travis-support-for-Linux.patch > > > The project does not currently have any continuous integration in place. > I've spent the last few days getting a working solution to consider. The > attached patch files add support for two commonly used services, > [Travis|https://travis-ci.org/] (Unix) and > [AppVeyor|https://www.appveyor.com] (Windows). > See this [GitHub > branch|https://github.com/rleigh-codelibre/xerces-c/commits/ci]. The last > commit has a green tick mark, which is the CI status. This links through to > the build results: > - > [Travis|https://travis-ci.org/rleigh-codelibre/xerces-c/builds/240825536?utm_source=github_status&utm_medium=notification] > - > [AppVeyor|https://ci.appveyor.com/project/rleigh-codelibre/xerces-c/build/1.0.76] > How to use this? Go to the Travis or AppVeyor websites and log in with > GitHub/BitBucket|GitLab credentials, or use you own public git repo. Enable > the service for your xerces-c git repo. Now any branch you push to your git > repo will be automatically built in several configuration combinations for > Lin
[jira] [Created] (XERCESC-2098) Add support for external continuous integration services
Roger Leigh created XERCESC-2098: Summary: Add support for external continuous integration services Key: XERCESC-2098 URL: https://issues.apache.org/jira/browse/XERCESC-2098 Project: Xerces-C++ Issue Type: Test Components: Miscellaneous Affects Versions: 3.2.0 Environment: Unix/Linux Windows (MSVC, Cygwin, MinGW) Reporter: Roger Leigh Attachments: 0001-samples-Makefile.am-Add-missing-continuation.patch, 0002-ci-Add-appveyor-support-for-Cygwin-MinGW64-and-MSVC1.patch, 0003-ci-Add-travis-support-for-Linux.patch The project does not currently have any continuous integration in place. I've spent the last few days getting a working solution to consider. The attached patch files add support for two commonly used services, [Travis|https://travis-ci.org/] (Unix) and [AppVeyor|www.appveyor.com] (Windows). See this [GitHub branch|https://github.com/rleigh-codelibre/xerces-c/commits/ci]. The last commit has a green tick mark, which is the CI status. This links through to the build results: - [Travis|https://travis-ci.org/rleigh-codelibre/xerces-c/builds/240825536?utm_source=github_status&utm_medium=notification] - [AppVeyor|https://ci.appveyor.com/project/rleigh-codelibre/xerces-c/build/1.0.76] How to use this? Go to the Travis or AppVeyor websites and log in with GitHub/BitBucket|GitLab credentials, or use you own public git repo. Enable the service for your xerces-c git repo. Now any branch you push to your git repo will be automatically built in several configuration combinations for Linux (Autotools, CMake) and Windows (CMake with Cygwin, MingGW64 and MSVC 2015). The exact combinations tested are viewable with the above build links, or in the attached patch files. The set of test combinations can be adjusted as desired. This could additionally be enabled for the Apache GitHub mirror or the Apache git repo itself, which would trigger builds for all subversion commits to do post-commit testing. Would there be any objection to committing these changes? -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
