MS Build Error: Cannot Include Boost Header
c:\projects\cflr-suite\src\Shared\cflrlic.git\ncflrlic\ncflrlic.vcxproj" (default target) (4) ->
(ClCompile target) ->
c:\projects\cflr-suite\src\DissoMaster\D2\packages\boost.1.58.0.0\lib\native\include\boost/preprocessor/repetition/repeat.hpp(19): fatal error C1083: Cannot open include file: 'boost/preprocessor/debug/error.hpp': No such file or directory [c:\projects\cflr-suite\src\Shared\cflrlic.git\ncflrlic\ncflrlic.vcxproj]
Added boost 1.58.0.0 to the project using Nuget package. App compiles without error on my development machine, however, I get a file not found error when using the AppVeyor build worker (VS2015RC). My development image is clean, meaning I don't have any versions of boost installed on my machine other than the Nuget package.
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Feodor Fitsner on 01 Jun, 2015 07:23 PM
Do you have package restore in "Before build script"?
2 Posted by tommyjohnw on 01 Jun, 2015 10:46 PM
I added that line but and rerun with the same results. Currently, I have the entire packages directory checked into source. So there was nothing to restore since all packages were present.
I don't quite understand how nuget configures the include path for my VC++ project but it seems to be working locally on my development machine.
Support Staff 3 Posted by Feodor Fitsner on 01 Jun, 2015 10:56 PM
I doubt that NuGet configures that either. Try adding some
dircommands to "before build" section to make sure those headers exist after repo is cloned. Check paths for any hardcoded/absolute values.4 Posted by tommyjohnw on 02 Jun, 2015 11:47 PM
I wasn't able to find the exact cause of my problem organizing my working directory, removing my packages directory from source control and re-adding the .nupkg resolved the issue.
Support Staff 5 Posted by Feodor Fitsner on 02 Jun, 2015 11:51 PM
OK, thanks for update.
Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:56 AM.