You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Additional information
Unfortunately the comma is part of the company name in the OneDrive location where Documents folder is. Changing the location of the Documents folder is not really feasible at scale.
One possible solution could be to use -Xlinker to specify rpath. See for example rust-lang/rust#38798.
This is a limitation of GCC which cannot be resolved by us. Paths cannot contain commas, cannot be network drives and cannot be longer than 260 characters. There is however a possible workaround:
Open the command prompt ("Start -> cmd")
Run "mklink /J "C:\OneDrive" "C:\Users\fasx1039/OneDrive - Xylem, Inc"
Load the file from C:\OneDrive\Documents/Hopsan/import/FMU/BouncingBall
This will create a link between your actual OneDrive folder and the temporary folder at C:\OneDrive, without moving the files. Please let me know if this works, as I cannot reproduce the problem myself.
Thanks for the reply! I don't think that will help, because Hopsan will ask Qt where the Documents folder is and store all imported FMUs there including generated C++ files.
Wouldn't it be possible to do something like: -Wl,--rpath -Xlinker "path/to/dir/with , in it". -Xlinker should pass the argument as-is.
That could be possible. I will have a look at it. We are in the process of rewriting the entire FMI import feature anyway, but this fix should be a low-hanging fruit.
Describe the bug
When importing an FMU and the Hopsan document path contains a comma, the linking stage fails.
To Reproduce
Expected behavior
Import should be successful.
Screenshots, Model or Data files
Hopsan version (please complete the following information):
HopsanGUI 64-bit, Version: 2.20.0.20220711.1354
Additional information
Unfortunately the comma is part of the company name in the OneDrive location where Documents folder is. Changing the location of the Documents folder is not really feasible at scale.
One possible solution could be to use -Xlinker to specify rpath. See for example rust-lang/rust#38798.
hopsan/HopsanGenerator/src/GeneratorUtilities.cpp
Line 210 in fc5ee1d
The text was updated successfully, but these errors were encountered: