Author Topic: Replacing compiler settings with a build script?  (Read 18026 times)

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 12296
    • Travis build status
Re: Replacing compiler settings with a build script?
« Reply #30 on: April 25, 2014, 11:33:03 pm »
Reproduced.
The problem happens, because the code expects that there is at least on program in the m_Commands member variable of the compiler, but for options_null.xml there are none.

@Alpha: Any idea how to fix this problem?

This is the problematic method: const CompilerTool& Compiler::GetCompilerTool(CommandType ct, const wxString& fileExtension) const
Returning a reference here is pretty bad and most of the times it is used as a pointer.
« Last Edit: April 25, 2014, 11:37:10 pm by oBFusCATed »
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 12296
    • Travis build status
Re: Replacing compiler settings with a build script?
« Reply #31 on: April 26, 2014, 04:23:37 pm »
Should be fixed in trunk...
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]