- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I would like to use the cydsfit.exe tool from the command line. There are many good reasons for doing so: build automation for example.
When building from within the Creator IDE the output provides the following command:
"c:\Program Files (x86)\Cypress\PSoC Creator\3.3\PSoC Creator\bin\cydsfit.exe" -.appdatapath "C:\Users\xxxx\AppData\Local\Cypress Semiconductor\PSoC Creator\3.3" -.fdsnotice -.fdswarpdepfile=warp_dependencies.txt -.fdselabdepfile=elab_dependencies.txt -.fdsbldfile=generated_files.txt -p C:\Users\xxxx\my_project\my_project.cydsn\my_project.cyprj -d CY8C4248LQI-BL483 -s C:\Users\xxxx\my_project\my_project.cydsn\Generated_Source\PSoC4 -- -yv2 -q10 -ygs -o2 -v3 -.fftcfgtype=LE
My immediate problem is that the source code generated from this command when run from the cmd.exe shell is placed in the same directory as our application code. i.e. the generated source code is placed in
C:\Users\xxxx\my_project\my_project.cydsn
not in
C:\Users\xxxx\my_project\my_project.cydsn\Generated_Source\PSoC4
When this command is run from the PSoC Creator IDE the generated code is placed in the correct directory Generated_Source\PSoC4.
What trickery is required to get the command line cydsfit.exe invocation to perform the same way as the IDE invocation?
Thanks,
-- Nat
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Just a guess: cydsfit places the output into the current directory, which is the directory from where you are running it. So CD into the target dir, and call the command from there. All paths given are absolute so this will work.