Artem Veschitsky opened 6 months ago
|
|||||
Is the path segment |
|||||
I am not familiar with msvc things. If possible, please attach an example project with detailed instructios on how to reproduce the issue so that I can test locally to see if things are fixed. |
|||||
I think yes its most long section in full path
I think you can have any content in file but path need equal like this And build system same AMBuild Install:
Usage:
After new prj we have 2 files
After editing:
Some main.cpp file:
|
|||||
Thanks for the detailed guide. Looks like msvc does not like long path. The workspace directory will be changed to use project id and build number combo to make it shorter. But I think this error may still occur when project files are nested deeper... |
|||||
Robin Shen changed title 6 months ago
|
|||||
OneDev changed state to 'Closed' 6 months ago
|
|||||
State changed as code fixing the issue is committed (d6279e5b) |
|||||
Referenced from commit 6 months ago
|
|||||
OneDev changed state to 'Released' 6 months ago
|
|||||
State changed as build #4264 is successful |
Type |
Improvement
|
Priority |
Normal
|
Assignee | |
Labels |
No labels
|
Now we have temp dir as
onedev-build3100065178529808779
but in windows this huge and msvc can't compile filefatal error C1083: Cannot open compiler generated file: '': Invalid argument
Maybe you can change to
onedev-build-(prj id-job number)
etc, as created docker networkCreating docker network 'agent-name-prj id-job number-???'...
create temp dir with prefix onedev-build
create temp file and using name as path