move res/ subdirectory to src/dmd/res/#11269
Conversation
|
Thanks for your pull request, @WalterBright! Bugzilla referencesYour PR doesn't reference any Bugzilla issue. If your PR contains non-trivial changes, please reference a Bugzilla issue or create a manual changelog. Testing this PR locallyIf you don't have a local development environment setup, you can use Digger to test this PR: dub run digger -- build "master + dmd#11269" |
6aea466 to
69f6d92
Compare
|
CyberShadow/DAutoTest says: where is that path specified? |
|
Line 74 in ca636dc |
|
Thanks @Geod24 as |
Alternatively, I would say that build files should not be mixed with source files. Having makefiles and |
|
Thanks @Geod24 but there appears to be yet another one: |
|
It seems unrelated to this failure, but I found one more case in ci.sh:test_dub_package. |
|
@kubo39 thanks, but where is that file? It's not in the dmd repository. |
|
@WalterBright |
|
thanks, trying it now |
|
same failure :-( |
|
Thank you. Blocked by dlang/dlang.org#2821 |
| targetType "library" | ||
| sourcePaths "src/dmd" | ||
| stringImportPaths "res" | ||
| stringImportPaths "src/dmd/res" |
There was a problem hiding this comment.
If you want to merge dlang.org PR without duplication, you need to temporarily add both directories here as dlang.org uses dmd as a library:
stringImportPaths "res"
stringImportPaths "src/dmd/res"
| <DCompile> | ||
| <VersionIdentifiers>MARS</VersionIdentifiers> | ||
| <StringImportPaths>..\..\res;$(OutDir)</StringImportPaths> | ||
| <StringImportPaths>../dmd/res;$(OutDir)</StringImportPaths> |
There was a problem hiding this comment.
| <StringImportPaths>../dmd/res;$(OutDir)</StringImportPaths> | |
| <StringImportPaths>..\dmd\res;$(OutDir)</StringImportPaths> | |
(similar for the changes below)
This is the Visual Studio project file, so I am pretty sure the Windows slashes should be kept.
You're not only there. However, |
In preparation for dlang#11269.
Ditto
dmd/.github/workflows/runnable_cxx.yml Lines 274 to 280 in d263f80 Lines 181 to 186 in d263f80 |
Oh Thanks for the correction @MoonlightSentinel. I wasn't aware that we were already doing this, but as these files are still in the same repo + under our control, I guess it's a now or never decision, because I believe packagers will soon switch to use |
|
(restarted all CIs by force-pushing) |
@CyberShadow any ideas? I wasn't able to reproduce this locally. |
|
Oh, no. Not another PDF problem. 😞 I don't know what happened there. A random fluke? |
|
The cure: dlang/dlang.org#2823 |
|
Thanks everyone for the help with this! There are more files like this that need fixing, but I'm a bit battle fatigued at the moment and will do them later. |
This ensures the resulting path is correct even for the sources distributed alongside the official releases. This is a regression introduced by dlang#11269.
This ensures the resulting path is correct even for the sources distributed alongside the official releases. This is a regression introduced by #11269.
Builds should not reference files up and out of the build directory and to the left.