Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

Crash with empty DLL target

<< < (2/3) > >>

killerbot:
I think the scripts should ask for a compiler !!! Always, maybe for this target I want to use another compiler then the project one. When the scripts do this --> there will be no bug at all ;-)

iw2nhl:
Yes, I read your [EDIT] part after my post.
You are definetly right: the scripts should ask for a compiler!

killerbot:
I have a current workaround like this :


--- Code: ---wxString Wiz::GetTargetCompilerID()
{
wxString CompilerId = CompilerFactory::GetDefaultCompilerID();
    if (m_pWizBuildTargetPanel)
    {
        CompilerId = m_pWizBuildTargetPanel->GetCompilerID();
        if(CompilerId == wxEmptyString)
        {
        CompilerId = CompilerFactory::GetDefaultCompilerID();;
// show message that no compiler stated and we falling back tpo the default one
        }
    }
    else
    {
    // show message that no compiler stated and we falling back tpo the default one
    }
    return CompilerId;
}

--- End code ---
The save(workaround) in the above mentioned examples is now carried out by that reassignemn of the default compiler set in CB. Might commit this code tomorrow, or could fall back on the project one. But note : this is a workaround, not the real place to fix.

iw2nhl:
Ok, it seems right.
At least with this C::B does not crash!
When the scripts will be updated, a message can be added so that a similar bug can be found rapidly in the future.
Thanks for the fast solution!

killerbot:
no problem, tomorrow I will commit, but the solution will be at the call of this method. So a little change.

Navigation

[0] Message Index

[#] Next page

[*] Previous page