Home → Questions →

Can we build the same project with MSYS and VisualStudio?

• Edit

human

Jun 27, 2017 @ 09:50 PM

I've just started with AppVeyor with a free and open source project and got the VisualStudio build working (currently with two workers: VS2013 and VS2017, both using the VS2013 project files) including the creation of the dist package (the project already had a cmd file for this).

I've tried to configure a third worker for doing the MSYS build (plain `configure && make`, but this doesn't seem to work (at least with the GUI options) as the options are the same for all workers.

Question: Do I need to create the same project with the same URLs again to check the MSYS build (and create the source tarball with `make dist`) or do other options exist for this scenario (maybe by using the appveyor.yml?)
Does the same apply if I want to test the cygwin build and MSYS64 build, too (all these have shown some bugs that occurred only there in the past, therefore I'd like to check all of these)?

1. 1 Posted by Ilya Finkelshte... on Jun 27, 2017 @ 10:16 PM

   

   Hi Simon,

   Ar you using standard MSBUILD option or SCRIPT option in UI for your Visual Studio builds?

   Ilya.

   • Edit

2. 2 Posted by human on Jun 27, 2017 @ 10:18 PM

   

   Hi Ilya, I'm currently using MSBUILD option in UI for the VS builds and the SCRIPT option in the MSYS-based project I've created in the meantime.

   • Edit

3. 3 Posted by Ilya Finkelshte... on Jun 27, 2017 @ 10:38 PM

   

   If you are OK to use SCRIPT with Visual Studio (actually msbuild) part, then you can squeeze all them together in the single build matrix.
   You are actually already using build matrix because you have 2 build worker images. You can add another dimension to the matrix with environment variables. Lets say you call it BUILD_TYPE and it can be MSBUILD and MSYS. So you call specific script depending on value of that variable.
   Adding this dimension to the matrix will generate 4 builds: 2 images x 2 variable values. But if you need only 3 (say you do not need VS2017 image with MSYS) you can exclude configuration from the matrix, but this feature exposed only in YAML.
   To move from MSBUILD to SCRIPT you can simple copy-paste command which AppVeyor uses from build log. To decide how much you loose if you move to SCRIPT, you need to understand if you are going to test multiple configurations, platforms and automatic packaging provided by AppVeyor.

   • Edit

4. Ilya Finkelshteyn closed this discussion on Aug 25, 2018 @ 02:18 AM.