Yeah, I just want to call the same makefile that works for this project. One of the challenges in our case is that we have 2 toolchains in the same project, and it seems like the IDEs assume you would only use one (m68k/sh)Chilly Willy wrote: I use Geany for my IDE... Geany even has a built in terminal so I don't have to open one if I don't want to. If you are using my latest examples that set all paths in the makefile instead of using environment variables, then it's very simple to use this with any IDE - just set the build option to make the makefile... you don't have to worry about environment variables.
Code Blocks has a lot of options for things like environment variables for a project, but I find that all too much for people to deal with. That's why I like simple makefiles with all the paths set in the makefile boilerplate. People really overcomplicate makefiles these days. Just because make allows stupidly complicated makefiles is no reason to actually do so.
I'll see if I can mold code::blocks to our makefile, otherwise, try out geany, it seems to have the main features I am looking for.
Edit: no luck with c::b so far. I am trying to use geany, where do you put the environment variables from the env.bat? In your user's environment variables? Or is there a way to specify these in the Make command when we call it in geany?
Code: Select all
@Echo Off SET GENDEV=C:\Users\Documents\roms\homebrew\_gcc\gen SET PATH=%GENDEV%\bin;%GENDEV%\sh-elf\bin;%GENDEV%\m68k-elf\bin;%GENDEV%\UTILS;%PATH% SET MAKE_MODE=unix Cmd "cd" /k