search for: compile_options

Well, I updated to cmake 2.8.12.2 but the result of changing that COMPILE_FLAGS to COMPILE_OPTIONS is that quotes are applied incorrectly: quotes are added surrounding the entire set of flags rather than around each individual item in the list. Obviously the build doesn't work (with the compiler looking for files named " -m64 ... ") but checking the relevant build command in build....

A couple of llvm sub-projects have been failing to build for me for a while (compiler-rt asan and util/unittests, at least). It turns out to be due to the fact that some paths on my system include spaces and other special characters, but the the build.ninja file was not generated with correctly quoted strings. Specifically I'm on OS X and the command is setting -isysroot to a location inside

On Nov 26, 2012, at 3:20 PM, Bill Wendling wrote: >> 4. Do we really want the attribute references limited to a number? Code will be more readable >> if you can use actual names that indicate the intent. For example: >> >> attrgroup #compile_options = { … } >> void @foo attrgroup(#compile_options) >> > The problem with this is it limits the number of attribute groups to a specific set -- compile options, non-compile options, etc.. There could be many different attribute groups involved, especially during LTO. I realize t...

...ll be represented internally to LLVM. Let me know if you have strong objections to this. > 4. Do we really want the attribute references limited to a number? Code will be more readable > if you can use actual names that indicate the intent. For example: > > attrgroup #compile_options = { … } > void @foo attrgroup(#compile_options) > The problem with this is it limits the number of attribute groups to a specific set -- compile options, non-compile options, etc.. There could be many different attribute groups involved, especially during LTO. I realize that the name...

...le: > > void @foo attrgroup(#1) alwaysinline attrgroup(#2) nounwind > > 4. Do we really want the attribute references limited to a number? Code will be more readable > if you can use actual names that indicate the intent. For example: > > attrgroup #compile_options = { … } > void @foo attrgroup(#compile_options) > > 5. Can attributes be nested? For example: > > attrgroup #1 = { foo, bar } > attrgroup #2 = { #1, baz } > > Might be nice. > > 6. Do we really need to specify the attrgroup keywo...

...nter-mixed? For example: void @foo attrgroup(#1) alwaysinline attrgroup(#2) nounwind 4. Do we really want the attribute references limited to a number? Code will be more readable if you can use actual names that indicate the intent. For example: attrgroup #compile_options = { … } void @foo attrgroup(#compile_options) 5. Can attributes be nested? For example: attrgroup #1 = { foo, bar } attrgroup #2 = { #1, baz } Might be nice. 6. Do we really need to specify the attrgroup keyword twice? (Once in the group definition and on...

Hi! This is a proposal to expand the Attributes class to support many different options that will be accessible by all parts of the compiler. Please read and give any feedback you may have. Thanks! -bw Passing Options to Different Parts of the Compiler Problem ======= There is a growing need to pass information from the front-end to different parts of the compiler, especially

...sources as long as target_sources() is used later * target_compile_{definitions,features,options}, target_include_directories(), target_sources(), and target_link_libraries() can set the corresponding INTERFACE_* properties on imported targets * COMPILE_DEFINITIONS supports generator expressions * COMPILE_OPTIONS source file property added * INCLUDE_DIRECTORIES source file property added * Interface libraries support custom properites CMake 3.12 (released July 17th 2018): * add_compile_definitions() added to add compile definitions for targets (to avoid the global pollution caused by add_definitions()) * c...

...sources() is used later >> * target_compile_{definitions,features,options}, target_include_directories(), target_sources(), and target_link_libraries() can set the corresponding INTERFACE_* properties on imported targets >> * COMPILE_DEFINITIONS supports generator expressions >> * COMPILE_OPTIONS source file property added >> * INCLUDE_DIRECTORIES source file property added >> * Interface libraries support custom properites >> >> CMake 3.12 (released July 17th 2018): >> * add_compile_definitions() added to add compile definitions for targets (to avoid the globa...

...sources as long as target_sources() is used later * target_compile_{definitions,features,options}, target_include_directories(), target_sources(), and target_link_libraries() can set the corresponding INTERFACE_* properties on imported targets * COMPILE_DEFINITIONS supports generator expressions * COMPILE_OPTIONS source file property added * INCLUDE_DIRECTORIES source file property added * Interface libraries support custom properites CMake 3.12 (released July 17th 2018): * add_compile_definitions() added to add compile definitions for targets (to avoid the global pollution caused by add_definitions()) * c...

...sources as long as target_sources() is used later * target_compile_{definitions,features,options}, target_include_directories(), target_sources(), and target_link_libraries() can set the corresponding INTERFACE_* properties on imported targets * COMPILE_DEFINITIONS supports generator expressions * COMPILE_OPTIONS source file property added * INCLUDE_DIRECTORIES source file property added * Interface libraries support custom properites CMake 3.12 (released July 17th 2018): * add_compile_definitions() added to add compile definitions for targets (to avoid the global pollution caused by add_definitions()) * c...

...sources as long as target_sources() is used later * target_compile_{definitions,features,options}, target_include_directories(), target_sources(), and target_link_libraries() can set the corresponding INTERFACE_* properties on imported targets * COMPILE_DEFINITIONS supports generator expressions * COMPILE_OPTIONS source file property added * INCLUDE_DIRECTORIES source file property added * Interface libraries support custom properites CMake 3.12 (released July 17th 2018): * add_compile_definitions() added to add compile definitions for targets (to avoid the global pollution caused by add_definitions()) * c...

...sources() is used later >> * target_compile_{definitions,features,options}, target_include_directories(), target_sources(), and target_link_libraries() can set the corresponding INTERFACE_* properties on imported targets >> * COMPILE_DEFINITIONS supports generator expressions >> * COMPILE_OPTIONS source file property added >> * INCLUDE_DIRECTORIES source file property added >> * Interface libraries support custom properites >> >> CMake 3.12 (released July 17th 2018): >> * add_compile_definitions() added to add compile definitions for targets (to avoid the glob...

...le_{definitions,features,options}, > target_include_directories(), target_sources(), and > target_link_libraries() can set the corresponding INTERFACE_* > properties on imported targets > * COMPILE_DEFINITIONS supports generator expressions > * COMPILE_OPTIONS source file property added > * INCLUDE_DIRECTORIES source file property added > * Interface libraries support custom properites > > CMake 3.12 (released July 17th 2018): > * add_compile_definitions() added to add compile definitions > for ta...

...sources as long as target_sources() is used later * target_compile_{definitions,features,options}, target_include_directories(), target_sources(), and target_link_libraries() can set the corresponding INTERFACE_* properties on imported targets * COMPILE_DEFINITIONS supports generator expressions * COMPILE_OPTIONS source file property added * INCLUDE_DIRECTORIES source file property added * Interface libraries support custom properites CMake 3.12 (released July 17th 2018): * add_compile_definitions() added to add compile definitions for targets (to avoid the global pollution caused by add_definitions()) * c...

...sources as long as target_sources() is used later * target_compile_{definitions,features,options}, target_include_directories(), target_sources(), and target_link_libraries() can set the corresponding INTERFACE_* properties on imported targets * COMPILE_DEFINITIONS supports generator expressions * COMPILE_OPTIONS source file property added * INCLUDE_DIRECTORIES source file property added * Interface libraries support custom properites CMake 3.12 (released July 17th 2018): * add_compile_definitions() added to add compile definitions for targets (to avoid the global pollution caused by add_definitions()) * c...

...later >> * target_compile_{definitions,features,options}, >> target_include_directories(), target_sources(), and target_link_libraries() >> can set the corresponding INTERFACE_* properties on imported targets >> * COMPILE_DEFINITIONS supports generator expressions >> * COMPILE_OPTIONS source file property added >> * INCLUDE_DIRECTORIES source file property added >> * Interface libraries support custom properites >> >> CMake 3.12 (released July 17th 2018): >> * add_compile_definitions() added to add compile definitions for targets >> (to avoid...

...g as target_sources() is used later > * target_compile_{definitions,features,options}, target_include_directories(), target_sources(), and target_link_libraries() can set the corresponding INTERFACE_* properties on imported targets > * COMPILE_DEFINITIONS supports generator expressions > * COMPILE_OPTIONS source file property added > * INCLUDE_DIRECTORIES source file property added > * Interface libraries support custom properites > > CMake 3.12 (released July 17th 2018): > * add_compile_definitions() added to add compile definitions for targets (to avoid the global pollution caused...