…ile. initially configure the correct build command

…details

…per target generation and configuration

…er...

…he compiler flags extracted... albeit assuming C language. Next to get the linker options extracted too

…ds properly in future. Works a bit less than before

…continue work.

…first successfull fastbuild build

…pecific targets aren't coming through properly

…m to be in the correct places

…generated to

…psulate all projects.. so structure may need to change again

…ppears hard to choose

…e options

…been requested in multiple places with the current code, I need to extract those out somehow

…l means we're linking the object twice. This may mean we should remove the reference for fastbuild, and instead set it as a preBuiltDependency instead

…e. Different languages need different compilers defined for them now. RC files aren't working for example

… called

…ave reserved characters in them that are unsuitable for variable definitions. Could have sanitised, but the structs weren't used anyway, so converted to a comment instead

…sn't implemented. Corrected cases where same compiler is used for multiple languages. Fastbuild does not like having the same compiler defined twice, so now it is indirected with variables.

…he dependency and linking the correct objs together

…ncorrect output directories were applied

…defined outputs. So need to merge all the custom commands against their outputs I suppose.

…id switch for cl.exe in msvc

…f the fastbuild bug is fixed

…absolute path to the cmd.exe that is popular with Cmake. Custom commands now execute. But the dependency graph is still incorrect, as it can define an output multiple times. Need to collect everything together and define those outputs only once.

…ions. I believe the ordering should be OK still though.

… comment

…t files weren't outputing to a unique location for release and debug builds. So I think they may have been overwriting eachother. - untested change, it may need fixing again

…o make it a little more understandable

…ed, but hopefully one of the unit tests exercises it

… closely related to custom commands

… commands and post build steps. Consulting with Franta on how to represent it best inside FASTBuild.

…ementation of it for FastBuild. This is important for object library obj file resolution. -ObjectLibrary unit test was failing without this. (still failing but closer)

…piling, after also making sure the INTDIR is defined. Doing that required pushing through a $ sign through the commandLine processing and then conversion back during commandline building.

…a custom command. Instead now detecting the variable directly and unescaping it. Also detecting it directly when determining if the custom command is configuration dependant. If it is, then it should be generating the custom command multiple times, instead of once like it was before.

…and how that is driven in cmake data. Added the appropriate check to be able to declare this properly now. Removed some dead code as well.

…st of items to link during a linker step, now they are.

…are defined in targets

…able instead. Making corresponding changes to fastbuild

…ects.

It was duplicating all obj's that need linking

Also adding detection for symbolic outputs from a custom command, and not listing them to FASTbuild.

… to always set as a txt file.

(same way the msvc generators do) - fixes linkdirectory unit test

Fixed a segfault in the recent code, so hopefully these unit test results will be different again. (takes 45mins to run though)

Fixes for linux and default (no c++11) gcc builds.
Basic changes to get linux/gcc (no c++11) builds working. Hopefully it still works with visual studio.

Missed moving one part out of a WIN32 section

…hanges

build warning fixes

This is for use with generator expressions that include ConfigName. A better solution needs to be found.

This appears consistent with Ninja generator behaviour and hopefully solves some gcc issues for use in linux

Distributable compile should be possible with this change (currently untested)

This solves issues linking to libraries that are on paths with spaces in them.

I needed to put Quotes around these placeholders, but the quotes would not stay when extracting the command from the front of the string. (They would be removed by the argument parsing code).
So instead I've used a placeholder with no quotes, and the quotes are preserved inside the placeholder's value.
The argument parsing code most likely needs to be removed from the equation entirely and custom code for extracting the executable at the front of the string written instead.
Once that is done, this code could be reverted back to the more sane version.

…being used.

* properly escape single quotes in strings
* re-ordered variables and pre-build  dependencies

…ame name as a source file

e.g. test.cxx and test.rc were both compiled to test.obj.
now test.rc is compiled to test.res

fixed RC generation

This is necessary as fastbuild uses windows' CreateProcess, which does not support output redirections with '>'.
This may work on linux, but I cannot test it.

The test 'CustomCommand' finally passes

Removed an unused function and an unused functor struct

FastBuild Generator: some fixes for custom command execution

Fastbuild does not behave the same as the makefile generator with relative paths.

Exclude Fastbuild from the CMP0021 test

Check if parent makefiles are excluded from all

…tput path per ObjectList accordingly

Source groups now break up files by directory so the output names don't collide

Also added MinSizeRel and RelWithDebInfo configurations.
Also make sure that no default configuration is passed in CMAKE_BUILD_TYPE.