search for: vc2k5

...d const to that functor, everything builds nice and fine (well, besides the ton of warnings), the example apps work, etc... and so forth. Thanks for the help though. But yes, let me say again, that functor still needs const added to it. It is correct for the spec, and it is required for at least VC2k5 (I tried building without it by removing my includes, libs, defines, and about ten other things, it is needed in every case, spent about 8 hours on all this so I am extremely sure). Attached is the patch; should I post it to the LLVM list as well? Oh, and yes, instead of VC2k5 being the minimum r...

...uot;standard" for building LLVM with VC++. >> >> If you have strong arguments against this, please voice them. > > As long as instructions are supplied on how to pass in user defined > macros to the build system. I have to turn off a lot of the extra > safety crap that VC2k5 and higher added [snip] > I am sure I am not the only one that does that, so supplying such > instructions for how to add in your own preprocessor definitions would > be great. For C source files: cmake -DCMAKE_C_FLAGS="-DSOME_DEF=value -DSOME_OTHER_DEF=value" path/to/llvm For...

I did some looking up on that const thing. Apparently that const is 'supposed' to be there, but it is not strictly required. However there is a bug in VS2k3 (VS7) through VS2k8 (VS9) (no clue if it has been fixed yet) that requires it to be there when the functor is being called through a const qualified interface, such as through stl containers. They state that a bug report has been

Chris proposed on IRC to remove the Visual Studio project files and turn CMake into the "standard" for building LLVM with VC++. If you have strong arguments against this, please voice them. -- Oscar

...turn > CMake into the "standard" for building LLVM with VC++. > > If you have strong arguments against this, please voice them. As long as instructions are supplied on how to pass in user defined macros to the build system. I have to turn off a lot of the extra safety crap that VC2k5 and higher added otherwise a program of mine takes 5 minutes to run (where with that safety crap disabled it takes about 15 seconds, no joke on the times). In the VC++ projects I just select them all, right-click, properties, C/C++, Preprocessor, Preprocessor definitions, and add 6 definitions in...

...uilding LLVM with VC++. >>> >>> If you have strong arguments against this, please voice them. >> >> As long as instructions are supplied on how to pass in user defined >> macros to the build system. I have to turn off a lot of the extra >> safety crap that VC2k5 and higher added > [snip] >> I am sure I am not the only one that does that, so supplying such >> instructions for how to add in your own preprocessor definitions would >> be great. > > For C source files: > > cmake -DCMAKE_C_FLAGS="-DSOME_DEF=value -DSOME_OTHE...

...Óscar Fuentes <ofv at wanadoo.es> wrote: >> OvermindDL1 <overminddl1 at gmail.com> writes: >>> As long as instructions are supplied on how to pass in user defined >>> macros to the build system. I have to turn off a lot of the extra >>> safety crap that VC2k5 and higher added >> [snip] >>> I am sure I am not the only one that does that, so supplying such >>> instructions for how to add in your own preprocessor definitions would >>> be great. >> [snip] > He's talking about how VC++ deprecated (with warnings)...