Fix MLModule post-build copy path for MSVC generators#802
Conversation
|
looks good to me, but I believe board controller and data handler use the same pattern and should be updated the same way |
|
Thanks! Before I update those, could you clarify the expected scope so I don’t over-apply the change:
If possible, I’d really appreciate as much detail as you can provide (e.g. specific files, targets, or patterns to update), so I can apply the fix correctly and keep the patch consistent. |
|
I think everything what uses pattern like Also with this is there a real need for: The idea to add this if else was to handle $CONFIG and different paths as a result for different OSes |
In the file you have changed this part probably can be removed now? Just make sure we dont copy it for ANDROID |
|
Thanks, I’ve updated the same pattern in ml, board controller, and data handler, while keeping Android logic and external dependency copies unchanged. |
|
Codex Review: Didn't find any major issues. Keep them coming! ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Fixes an inconsistency in
src/ml/build.cmakewhere MSVC POST_BUILD steps assume a config subdirectory (compiled/$<CONFIG>/...) while output is set tocompiled/.Replaces hardcoded source paths with target-based generator expressions:
$<TARGET_FILE:${ML_MODULE_NAME}>$<TARGET_LINKER_FILE:${ML_MODULE_NAME}>This improves compatibility with single-config generators (e.g. Ninja in CLion) where artifacts may not be placed in config-specific subdirectories.
Related to #255 and #604.