Error "Cannot match vs include prefix" #14
Comments
|
I've added explicit error message. Could you try it again? |
|
This is what I get when I try |
|
Very helpful! Let me try to fix this. |
|
No problem. Let me know if I can help in any way! |
|
Also can you send me |
|
|
Ok, try next binary. Post outputs, also please check directories near ps.: Thank you for your support! :) |
The DLL is present in PS: No problem, it's well deserved! |
|
It's strange. Maybe you could try to run those commands (from output) in cmd window? |
|
Oh, there won't be the source file there |
|
I didn't think about trying SW from Windows CMD, here is the output: (I don't use CMD, I use Git Bash so there may be an env mismatch somewhere) |
Oh. I'll try, maybe I can repro it locally. Your log is ok now. Show your build script. From what I see, you need to fix packages (deps) from |
|
I don't have a build script yet, I didn't migrate so it's using my I'll try to create a |
|
I see. SW have some beginner support for CPPAN syntax (cppan.yml). |
Ok, let me know if I can do anything else!
Yes, I noticed that. I'm writing my |
|
This is exactly for shared build. |
|
I hope you don't mind if I hijack this issue for asking help regarding my new Here it is: void build(Solution& s)
{
auto& engine = s.addTarget<StaticLibraryTarget>("engine");
{
engine.CPPVersion = CPPLanguageStandard::CPP17;
// Files
engine.Private += "Projects/Engine/Source/.*"_rr;
engine.Private += "Projects/Engine/Include/.*"_rr;
engine.Private += "Dependencies/json/Json.cpp";
engine.Private += "Dependencies/json/Json.h";
engine.Private += "Dependencies/json/Json-forwards.h";
// Dependencies
engine.Private += "org.sw.demo.boost.filesystem-1.68.0"_dep;
// Include directories
engine.Public += "Projects/Engine/Include"_id;
engine.Public += "Dependencies/json"_id;
engine.Public += "Dependencies/glm/include"_id;
engine.ApiName = "RAYON_ENGINE_API";
}
auto& cli = s.addTarget<ExecutableTarget>("cli");
{
cli.CPPVersion = CPPLanguageStandard::CPP17;
// Files
cli.Private += "Projects/CLI/Source/.*"_rr;
cli.Private += "Projects/CLI/Include/.*"_rr;
cli.Private += "Projects/Engine/Include/.*"_rr;
cli.Private += "Dependencies/json/Json-forwards.h";
// Dependencies
cli.Private += engine;
cli.Private += "org.sw.demo.boost.filesystem-1.68.0"_dep;
cli.Private += "org.sw.demo.boost.program_options-1.68.0"_dep;
// Include directories
cli.Private += "Projects/CLI/Include/"_id;
cli.Private += "Dependencies/glm/include"_id;
}
}I get this error when I |
|
Just use the latest boost (hope it's ok for you). Older versions are not updated for sw changes. |
|
Ok thank you, that worked! And how would I convert the following local_settings:
local_build: true
build_dir: ./.cppan/build
build:
generator: Visual Studio 15 2017
configuration: Release
root_project: rayon |
This is not very customizable yet. Outputs will be in Also FYI: sw is able to generate very cool VS solutions. Just use |
It's good that it can generate VS solutions. I may give it a try since I'm using VSCode for now. (I do JS dev at work so I'm used to its configuration) |
We have
Default config is release+shared build. You already can use any combination on command line you want:
Yeah, my knowledge comes from studying MS VS versions. And listing would be nice, but it's about documentation task. I'm pretty close to start working on it.
I'll think about it. We are talking here mostly in question-answer mode. If you miss some feature more than that, feel free to open separate issue. It's simpler to track them for me also. |
|
This issue is fixed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Attempting to run
sw buildin my project prints the following error:Exception in file D:\dev\cppan2\client2\src\sw\builder\command.cpp:1323, function detectMsvcPrefix: Cannot match vs include prefix.This is probably environment related, I don't think it is easily reproducible.
Expected behavior
I expected
swto build my project.To Reproduce
Steps to reproduce the behavior:
sw buildInformation:
Git bashfor Windows, in case it matters. (Latest version as of today)The text was updated successfully, but these errors were encountered: