Recent Posts

91

Help / Re: Original Post-compile message in the build log?

« Last post by nore on May 21, 2023, 05:04:53 pm »

Try doing just build or re-build instead of the Build and run option.

Yes sir, this is what I normally do unless I am testing updates.

Here is the build log output:

-------------- Build: Debug in console (compiler: GNU GCC Compiler)---------------

g++.exe -Wall -g -g -IC:\mingw64\include\c++\12.2.0 -IC:\mingw64\x86_64-w64-mingw32\include\gdiplus -IC:\mingw64\x86_64-w64-mingw32\include -c "C:\Users\-------\Desktop\Programs\CodeBlocks Projects\console\main.cpp" -o obj\Debug\main.o
g++.exe -LC:\mingw64\x86_64-w64-mingw32\lib -LC:\mingw64\lib -o bin\Debug\console.exe obj\Debug\main.o   
Output file is bin\Debug\console.exe with size 152.94 KB
Process terminated with status 0 (0 minute(s), 5 second(s))
0 error(s), 0 warning(s) (0 minute(s), 5 second(s))

The last two lines are blue and italicized, but the output message seems to have changed, if I am correct. I do not remember changing a setting, just one day receiving a different message upon a successful build.

92

Help / Re: Original Post-compile message in the build log?

« Last post by stahta01 on May 21, 2023, 04:46:39 pm »

Try doing just build or re-build instead of the Build and run option.

Tim S.

93

Help / Original Post-compile message in the build log?

« Last post by nore on May 21, 2023, 12:18:21 pm »

Hi there, I have been using code::blocks for many months now without issue. It is my favorite IDE. I remember there being an original message sent to the build log with bold blue text after a successful compile; but now in my build log there is only italicized blue text: "Process terminated with status 0" with the compile time and diagnostic information (errors, warnings) included with it. I am not sure what caused this change but I would prefer the original compile message -- does anyone know how to fix this?

94

Plugins development / Re: Plugin 'compilergcc'

« Last post by LETARTARE on May 20, 2023, 05:23:54 pm »

I don't think so. But this needs to be checked by other people.
It would then be necessary to delete the code presented first, which is no longer useful.

There is the same kind of code for 'int CompilerGCC::RunSingleFile(const wxString& filename)'.

95

Plugins development / Re: Plugin 'compilergcc'

« Last post by killerbot on May 20, 2023, 04:46:57 pm »

I agree, providing the user to click on something while we (the system) knows this is not possible, is not user friendly.

Would there still be added value in checking afterwards ... ?

96

Plugins development / Plugin 'compilergcc'

« Last post by LETARTARE on May 20, 2023, 04:00:55 pm »

With the 'compilergcc' plugin in 'int CompilerGCC::Run(ProjectBuildTarget* target)' we find

Code

 Manager::Get()->GetLogManager()->Log(_("Checking for existence: ") + f.GetFullPath(), m_PageIndex);
    if ( (target->GetTargetType() != ttCommandsOnly) && !wxFileExists(f.GetFullPath()) )
    {
        int ret = cbMessageBox(_("It seems that this project has not been built yet.\n"
                                 "Do you want to build it now?"),
                               _("Information"),
                               wxYES_NO | wxCANCEL | wxICON_QUESTION);
        switch (ret)
        {
            case wxID_YES:
            {
                m_pProject->SetCurrentlyCompilingTarget(0);
                m_RunAfterCompile = true;
                Build(target);
                return -1;
            }
            case wxID_NO:
                break;
            default:
                m_pProject->SetCurrentlyCompilingTarget(0);
                return -1;
        }
    }

This verifies that the executable exists, because '&Run' has been activated.

Instead, '&Run' should be invalidated if the executable does not exist. This could be done automatically in
'void CompilerGCC::OnUpdateUI(wxUpdateUIEvent& event)' by :

Code

    ...
    cbProject* prj = projectManager->GetActiveProject();
    cbEditor* ed = Manager::Get()->GetEditorManager()->GetBuiltinActiveEditor();
/// new
    if (id == idMenuRun)
    {
        event.Enable(exeExists(prj));
    }
    else
    ...

with 'exeExists(prj)' which would indicate whether the executable exists for example :

Code

bool CompilerGCC::exeExists(cbProject* prj)
{
    bool valid = false;
    if (prj)
    {
        ProjectBuildTarget* pTarget = prj->GetBuildTarget(prj->GetActiveBuildTarget());
        if (pTarget)
        {
            wxString out = UnixFilename(pTarget->GetOutputFilename());
            Manager::Get()->GetMacrosManager()->ReplaceEnvVars(out);
            wxFileName file(out);
            file.MakeAbsolute(prj->GetBasePath());
            valid = ::wxFileExists(file.GetFullPath());
            valid = valid || (pTarget->GetTargetType() == ttCommandsOnly) ;
        }
    }

    return valid;
}

This approach seems to me to be more correct than checking afterwards whether the action taken is correct.
Because in the options allowed to the user: the option 'wxID_NO' leads to run anyway with an error !!

What do you think about this?

97

Development / Re: to which compiler should we step up to bundle with CB

« Last post by killerbot on May 20, 2023, 03:37:10 pm »

I have successfully build with this "https://github.com/brechtsanders/winlibs_mingw/releases/download/13.1.0-16.0.2-11.0.0-ucrt-r1/winlibs-x86_64-mcf-seh-gcc-13.1.0-llvm-16.0.2-mingw-w64ucrt-11.0.0-r1.zip"

• wxwidgets 3.2.2.1
• CB trunk

First runs seem to be ok.

I think this is a compiler bundle worth using ...
Maybe as the base for the next nightly ... ?

98

Development / Re: UI for project globs aka automatic source directories

« Last post by BlueHazzard on May 19, 2023, 11:37:12 pm »

Can you test this second patch? Specially code completion and so on...
Also it would be interesting, if you could test if you specifically remove the link project file tick in file->properties->build and if this still is persisted in your case
I think this would not work, and i do not think there is a solution for this...
Are you using windows? Are you using some sync application on the source files?

99

Development / Re: to which compiler should we step up to bundle with CB

« Last post by killerbot on May 19, 2023, 07:57:00 pm »

didn't know that one existed, cool, but seems outdated.

PCH problems, hmm, as my track record in this forum shows, I hate them, they are nothing but troubles ;-)

100

Development / Re: to which compiler should we step up to bundle with CB

« Last post by Miguel Gimenez on May 19, 2023, 07:06:15 pm »

I have checked the Nuwen distro from Stephen T. Lavavej, it includes GCC 11.2.0 and Boost 1.77, and works fine except for two annoyances:

- The included binutils has a linking bug that can be solved deleting a flie from the distro
- C::B does not compile due to PCH problems (lot of errors from MapViewFileEx). I do not know if this is a problem from the distro or from GCC 11.2