Bug #7776 2006-06-06 22:29
vahur
$objects_output_dir conflicts with $objects variable
It happens when you use $objects_output_dir in project build options->Compiler->Other options. $objects_output_dir gets expanded to contents of $objects variable plus _output_dir. For example if I am compiling src\main.cpp $objects = .release\src\main.obj and $objects_output_dir expands to .release\src\main.objs_output_dir.
- Category
- Application::WrongBehaviour
- Group
- Status
- Closed
- Close date
- 2006-09-08 11:39
- Assigned to
History
PS. It happened with build jun 6 2006 ver 1.0 revision 2537 windows
when I implementedt his, I ran into the same problem and then I did this :
if (target)
{ // this one has to come first, since wxString::Replace, otherwise $object would go first
// leaving nothing to replace for this $objects_output_dir
macro.Replace(_T("$objects_output_dir"), target->GetObjectOutput());
}
macro.Replace(_T("$compiler"), compilerStr);
macro.Replace(_T("$linker"), compiler->GetPrograms().LD);
macro.Replace(_T("$lib_linker"), compiler->GetPrograms().LIB);
macro.Replace(_T("$rescomp"), compiler->GetPrograms().WINDRES);
macro.Replace(_T("$options"), m_CFlags[target]);
macro.Replace(_T("$link_options"), m_LDFlags[target]);
macro.Replace(_T("$includes"), m_Inc[target] + fileInc);
macro.Replace(_T("$res_includes"), m_RC[target] + fileInc);
macro.Replace(_T("$libdirs"), m_Lib[target]);
macro.Replace(_T("$libs"), m_LDAdd[target]);
macro.Replace(_T("$file"), file);
macro.Replace(_T("$dep_object"), deps);
macro.Replace(_T("$object"), object);
macro.Replace(_T("$resource_output"), object);
Weird you still have it, could you provide a test project for me in which you can reconstruct the issue ?
Report is closed.
Note: This is a preformatted standard message.
Possible reasons for closing this report are:
* the developer in charge of the issue
- could not reproduce it despite trying several times
- did not get sufficient information
- got no reply to an inquiry for specific information
* the report is quite a bit dated of now, and
- no user comments have been added for several weeks
- significant changes have been made to the code
- no other developer could reproduce it either
It is assumed that the problem does not persist and the report
can be closed.
If the problem reappears in future releases, please feel free to
re-open this report and provide precise information on how to
reproduce it.