How are you invoking make? Does Dev-C++ do it for you?
Make sure your indented lines are indented with a tab. Spaces don't work. And make sure your editor doesn't automatically convert spaces to tabs. (Use Notepad if it does.)
Wait a minute, did you write that makefile?
dwk
Seek and ye shall find. quaere et invenies.
"Simplicity does not precede complexity, but follows it." -- Alan Perlis
"Testing can only prove the presence of bugs, not their absence." -- Edsger Dijkstra
"The only real mistake is the one from which we learn nothing." -- John Powell
Other boards: DaniWeb, TPS
Unofficial Wiki FAQ: cpwiki.sf.net
My website: http://dwks.theprogrammingsite.com/
Projects: codeform, xuni, atlantis, nort, etc.
No
--Stephen
When I try to compile project is just appear as so to speak.
--Stephen
Okay. Well then, take ZuK's suggestion and make a new project. One without spaces in the path.
dwk
Seek and ye shall find. quaere et invenies.
"Simplicity does not precede complexity, but follows it." -- Alan Perlis
"Testing can only prove the presence of bugs, not their absence." -- Edsger Dijkstra
"The only real mistake is the one from which we learn nothing." -- John Powell
Other boards: DaniWeb, TPS
Unofficial Wiki FAQ: cpwiki.sf.net
My website: http://dwks.theprogrammingsite.com/
Projects: codeform, xuni, atlantis, nort, etc.
Ok
--Stephen
Morning Guys,
I'm having the same problem with Dev-C++, it really doesn't matter how you quote the targets, the generated makefile chokes gmake.
I'd thought the issue wasn't just spaces in target names, but the colon after the drive letter, and I'd been trying to figure out how to 'properly' mount, (as in unix) or reference by relative path, the directories of interest, so I could avoid the embedded colon. That was such a misery (gack, hate windows) that I ended up here, looking for a gmake switch that allowed DOS style paths.
Ah well, guess I'll try to re-organize this all onto a single network mount point, what a pain.
