Menu

#548 Problems with the relative path of Makefile option

open
None
5
2012-09-26
2005-04-25
dirmg
No

I'm using Dev-C++ 4.9.9.2
and find a problem about the relative path of specified
Makefile

First, in the Project Options->Build Options, I specified
the EXE path and OBJ path, with such values
as "..\debug" and "..\debug". It is because when "debug"
is given, there will be warning message appears "could
not create executable output directory". This problem is
also mentioned by "http://sourceforge.net/tracker/?
group_id=10639&atid=110639&func=detail&aid=1123313
"
While, on the same time,
in the Project Options->Makefile->use my own Makefile,
I select the Makefile file which is in the same path as
the project by the browse button system provided, and it
puts the filename simply in the corresponding text field
without path infomation. Then, I click the OK button to
confirm my changes. Problem is when I open this
Options Window second time, the value just specified is
missed, ie, not saved, leaving the check box unchecked.

I checked the source file "ProjectOptionsFrm.pas" and
in line 414-417 find
if cbUseCustomMakefile.Checked and FileExists
(edCustomMakefile.Text) then
fProject.UseCustomMakefile := true
else
fProject.UseCustomMakefile := false;
So, I think this is still the problem about relative paths.
and since the Makefile field is not allowed to edit, I edit
the "GIZA.dev"
UseCustomMakefile=1
CustomMakefile=C:\ABSOLUTEPATH\Makefile.win
then, it works well.
Here,
CustomMakefile=..\Makefile.win
is not accepted.
I don't know the reason.

May this problem be resolved in next version.

Discussion


Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.