|
|
|
This thread is locked; no one can reply to it.
|
| 5.1 branch #include headers; how to keep separate from 5.0 header files |
|
wonsungi
Member #11,799
March 2010
 |
I just downloaded Allegro 5.1 from SVN and tried building it with MSVC 10. I get a build error: ..\allegro.git\5.1\src\win\d3d_disp.cpp(34): fatal error C1083: Cannot open include file: 'allegro5/internal/aintern_shader_cfg.h' I know I need to copy the #include headers to some place MSVC can find them. How are the (addon) #include files normally "installed?" I noticed a comment that this might be a CMake/MSVC issue (http://www.allegro.cc/forums/thread/604502/873645#target) Is CMake just in charge of copying the addon header files to the build "include/allegro5" folder? update: aintern_shader_cfg.h needs to be built, so a simple copy is not possible. Other files like aintern_ttf_cfg.h exist; how do I figure out why aintern_shader_cfg.h was not built? Also a related question: the 5.0 and 5.1 header files may cause MSVC compile-time conflicts. What is the best way to keep the two sets of #include headers separated so 5.0 and 5.1 can be used at the same time? Is there any better method than modifying%INCLUDE% from vcvars32.bat?
|
|
Slartibartfast
Member #8,789
June 2007
 |
You can change your include directories as a project definition, and if you want two possible settings for the same project you can add and change project configurations and have one configuration configured to use one include directory and another another. ---- |
|
|
