Hello,
we have the following code Structure of a MCUXpresso Project.
Root/board/clock_config.c
Root/board/clock_config.h
Root/board/periperals.c
Root/board/periperals.h
Root/board/pin_mux.c
Root/board/pin_mux.h
Root/source/firmware_main.cpp
Root/Tools/bootloader/project/bootloader/board/
Root/Tools/bootloader/project/bootloader/board/clock_config.c
Root/Tools/bootloader/project/bootloader/board/clock_config.h
Root/Tools/bootloader/project/bootloader/board/periperals.c
Root/Tools/bootloader/project/bootloader/board/periperals.h
Root/Tools/bootloader/project/bootloader/board/pin_mux.c
Root/Tools/bootloader/project/bootloader/board/pin_mux.h
Root/Tools/bootloader/project/bootloader/board/firmware_main.cpp
Root/Tools/bootloader/project/bootloader/bootloader.mex
Root/firmware.mex
In the root folder there is the firmware and in a subfolder Tools there is the bootloader.
Both projects contain a .mex file. Upon code generation the Config Tools always write into the Tools/bootloader subfolder even for the Firmware Project.
Is there a way to configure in which folder the generated code is placed?
I would expect: Firmware.mex writes to Root/board and bootloader.mex writes to Root/Tools/bootloader/project/bootloader/board/.
The problem started to occur now, as we integrated boot projects into one folder tree.
I'm able to build just fine, as the bootloader subproject is "excluded from build".
I found a solution / workaround -> Exclude the Subfolder using the Resource Filters
Hi Tommy,
can you build you application?
Currently ConfigTools consider all files inside the project folder as "project files" and returns first clock_config.c that is found.
I'm not aware of any workaround, I'd recommend to split projects into two separate folders.
Regards
Marek