summaryrefslogtreecommitdiff
path: root/configure.ac
Commit message (Collapse)AuthorAgeFilesLines
* Visual Studio builds: "Add" Visual Studio 2019 projectsHEADmasterChun-wei Fan2019-06-181-0/+1
| | | | | | | Copy and update the relevant items in the visual Studio 2010 projects so that we have project files that is usable out-of-the-box in Visual Studio 2019, like what we did for the Visual Studio 2012~2017 projects.
* Post release version bumpIgnacio Casal Quinteiro2017-04-061-1/+1
|
* configure.ac: Bump LIBCROCO_MICRO_VERSIONChun-wei Fan2017-03-011-1/+1
| | | | We need to bump the micro version here as well...
* Visual Studio builds: Move projects to win32/Chun-wei Fan2017-02-231-10/+9
| | | | | | This enables us to go one less layer down the tree to reach the projects and allows the autotools modules Makefile-newvs.am and Makefile.msvcproj be in sync with the latest ones in GLib master.
* Visual Studio builds: Support Visual Studio 2017Chun-wei Fan2017-02-151-0/+8
| | | | | | | | | | | | | This updates the autotools scripts so that we can support Visual Studio 2017 by copying the 2010 projects and update items in there as needed. Note that the format of the toolset version string changed for Visual Studio 2017, so allow a custom toolset version string to be passed in and used, otherwise the platform toolset string is generated as before. Note also that Visual Studio 2017 aims to be compatible with 2015 on the CRT level, so one should be able to use 2017-built binaries with 2015-built binaries without problems.
* Post release version bumpIgnacio Casal Quinteiro2015-12-171-1/+1
|
* Post release version bumpIgnacio Casal Quinteiro2015-12-131-1/+1
|
* Post release version bumpIgnacio Casal Quinteiro2015-10-311-1/+1
|
* configure: specify config macro dirIgnacio Casal Quinteiro2015-10-311-0/+1
|
* configure: bump the prereqIgnacio Casal Quinteiro2015-10-311-1/+1
|
* configure: generate xz on distcheckIgnacio Casal Quinteiro2015-10-311-1/+2
|
* MSVC Builds: "Add" Visual Studio 2015 ProjectsChun-wei Fan2015-09-251-0/+1
| | | | | | This "adds" Visual Studio 2015 projects by doing what we did before: Copy the Visual Studio 2010 projects and updating items in there as needed, as the 2010 projects are largely the same to the 2015 ones.
* MSVC Builds: Add Simple Support for MSVC 2012/2013Chun-wei Fan2014-12-191-0/+2
| | | | | | | | | | | As the Visual Studio 2012/2013 project file format is largely the same as the Visual Studio 2010 ones, we can add support for them with relative ease by copying the 2010 files and updating them as necessary with autotools scripts, so to keep them up-to-date, all that is needed is that the Visual Studio 2010 projects are kept up to date. This might change if we do support the stack under the Windows RT APIs, but this will do the job for now.
* MSVC Builds: Split up the Property SheetsChun-wei Fan2014-08-081-2/+2
| | | | | | | | | | | | Update the Visual Studio Projects so that the property sheets are split by the functions required, so to simplify their maintenance. The projects can then import the property sheets that suit their needs. This is done like the rest of the GTK+ stack, so it also makes it easier to support newer versions of Visual Studio. As the original main property sheet is generated during configure time (and disted), update configure.ac as well, as the name of the template file changed in the process.
* build: rename configure.in into configure.acbaserock/morphNuno Araujo2013-01-201-0/+178
With the upcoming version of automake (1.14) the support for the configure.in file will be dropped.[1] [1]http://lists.gnu.org/archive/html/automake/2012-12/msg00038.html Bug #692111.
View Lorry Controller Status