is it possible to compile project from Makefile ?, is there anyway to import Makefile (pic32-gcc) ??.
I have been struggling since few days, providing own compilation flags, including own linker script -didn’t helped. Declaring board -force compiler to use board linkers -which cannot be found, used to see arrors like: pic32-cpp.exe: error: : No such file or directory.
Does make sense to use this framework for such task ??
When you choose to use PlatformIO you are using its build and configuration system (docs), which is itself based on the SCons build system. It isn’t supposed to compile your makefile project. However I’m sure you can get the project to compile the PIO way with the proper definitions and configuration.
The PIC32 framework is supported so if you have any errors with that we would need to know the code you’re trying to compile and your platformio.ini.
Also, you seem to be including the header of a library here for the USB functionality, but using this only the header is included, the code itself is not compiled; this will lead to undefined reference errors, the USB library code must be placed inside the project (e.g. as a lib/ folder)
Two linker files, one of which is a .x file? How does that work?
You have a double -L there and a double //. Also you seem to want to add a path to the library search path but which exact .a libraries must you include from there? The -l flags are missing here.
basically -need to compile it for 250F128B, project is for 220F032B …which is discontinued and id very hard to get hold of one.
elf32pic32mx.x -it’s a pinguino related stuff-USB Pinguino Bootloader, I can use any 32MX250F128B dev-board, I have chosen chipKit-DP32 for now…
Probably Makefile from project will be more informational regarding linking USB functionality…
what’s the -l flags are ??, I can’t pass -v to compiler, getting- pic32-gcc.exe: error: unrecognized command line option ‘-v,’
seems to be completely ununderstandable …way it works, passes the parameters