Recent Posts

81

Nightly builds / Re: The 01 September 2023 build (13344) is out.

« Last post by Miguel Gimenez on September 10, 2023, 02:07:43 pm »

Thank you for reporting and the exhaustive information.

Commits in the range 13159-13166 are not related to global variables, are you sure 13159 works and 13166 does not?

82

Development / Re: Loop in VarManagement on Linux wx30

« Last post by Pecan on September 10, 2023, 02:14:21 am »

This loop showed up on Windows wx322 also.
Fixed in Head r13350

83

Using Code::Blocks / Re: #define error in CodeBlocks

« Last post by stahta01 on September 09, 2023, 10:32:45 pm »

You can post a link to the FAQs but, you can't make the poster read and understand them.

Tim S.

84

Using Code::Blocks / Re: #define error in CodeBlocks

« Last post by PsychadelicGumballMachine on September 09, 2023, 04:33:54 pm »

While I thank you for the actual answer, I will not be back here ever. This place, much like stack overflow, is one of the most unpleasant places I've ever been on the internet (which given the internet, is really saying something). It will never cease to amaze me that people on here are as unhelpful, rude, nasty and down right toxic as they are given that they are quickly being replaced by ChatGPT and the like (which I also use. ChatGPT didn't have an answer for this one). Imagine running a business and yelling at your customers to the point where they don't want to come back and then wondering why your business failed.

85

Nightly builds / Re: The 01 September 2023 build (13344) is out.

« Last post by eckard_klotz on September 09, 2023, 03:07:55 pm »

Dear All.

Thanks to all developers for the ongoing effort in the further development of Code::Blocks.

After some month I decided use the new nightly 13344 (01.09.2023) to update Code::Blocks from the version used before 13107 (10.12.2022)

Unfortunately, I had to face an issue again, that I have already reported for the nightly 22.01.2022 (12672) here:
https://forums.codeblocks.org/index.php/topic,24820.msg169254.html#msg169254.

Code::Blocks is not able to recognize the compiler tool-chain configuration done in the conf-file by using global variables.
Please see the attached zip-file for the current screenshots:

• MinGW_12_2_0_64msvc_MSYS.conf : the conf-file I choose by using the personality dialogue.
• CB_13344_compilers_autodetection.png: the first information page I get now regarding the missing compiler tool suit.
• CB_13344_compiler_toolchain_executables.png: the partly overwritten list of build-tools actualy completly filed with global variables.
• CB_13159_compiler_toolchain_executables.png: the correct ist of build-tools filed with global variables.

As mentioned the same issue was already reported by me 22.01.2022 (12672).  You have solved the issue with the nightly from 06.02.2022 (12705).
Thus, I hope the description there is detailed enough  and I don't have to repeat it here again. However, don't hesitate to ask me for details you miss.


I tested some older releases between 13107 and 13344 to figure out when the issue was introduced again:

• 13344 bug is present
• 13268 bug is present
• 13231 bug is present
• 13166 bug is present
• 13159 works as desired
• 13107 works as desired

Thus I assume that the issue was introduced again between the revision 13159 (22.01.2023) and the revision 13166 (29.01.2023).


By the way: I'm working with windows 10 (frequently updated) on a laptop.

Best Regards,
                     Eckard Klotz.

86

Using Code::Blocks / Re: #define error in CodeBlocks

« Last post by fredIcn on September 09, 2023, 02:59:44 pm »

Suggestion:
PsychadelicGumballMachine, start troubleshooting from the basics. Create and run a brand new test C project. After confirming that it compiles and run, in the 'helloWorld' code that was created automatically insert the #define and recompile. The issue should not occur, which makes the environment or particularly the affected project the prime suspect. The issue you report is not reproducible
To cover every angle, in case the basic 'helloWorld' code does have the issue when you add the #define, then please follow previous advise and provide the requested logs to the original thread. Opening a new thread with the same question is not right, a breach of  protocol; lesson learned we hope.

87

Using Code::Blocks / Re: #define error in CodeBlocks

« Last post by stahta01 on September 08, 2023, 08:05:38 pm »

Since you failed to post a full build log, I have decided you no longer want help from me.

Edit2: See also https://forums.codeblocks.org/index.php/topic,25519.msg173716.html#msg173716

Good Bye.

Tim S.

88

Using Code::Blocks / Re: #define error in CodeBlocks

« Last post by PsychadelicGumballMachine on September 08, 2023, 07:26:23 pm »

I did. It said to specify the build of codeblocks you're using, your OS details, etc. So I did that, to the best of my ability at least.  It also had stuff about how to bracket code so that it was easily distinguishable from other text, but that doesn't apply here. I figured it was best to open a new one rather than modify the original as people would be more likely to see it, dismiss it because it was missing info and not come back to it.

89

Help / Re: #define error in CodeBlocks

« Last post by stahta01 on September 08, 2023, 12:30:57 am »

If you really think it is a Code::Blocks problem post a full build log.
If you do not, then post your code and the full build log on a website that helps newbie coders.

Tim S.

90

Development / Re: Loop in VarManagement on Linux wx30

« Last post by Pecan on September 07, 2023, 08:07:40 pm »

The following code succeeds to stop the infinite loop, and properly sets the global var, but I'm not sure about what to return when userVariableMgrIsBusy is true. See code at uservarmanager.cpp line 172

Help please.

Code

        else
        {
            // Guard against an infinite loop here because this code is rooted in the wxAppBase::DoIdle()/OnUpdateUI() event
            // and is called over and over until the "Global Variable Editor dialog" is dismissed.
            if (userVariableMgrIsBusy)
                return value;
            // Instantiation/deallocation of this struct acts as a semaphore code guard.
            // Any return from this point will seet the guard to false.
            struct usrVarMgr_t
            {
                usrVarMgr_t()  { userVariableMgrIsBusy = true; }
                ~usrVarMgr_t() { userVariableMgrIsBusy = false; }
            } UsrVarMgr;

            wxString msg;
            msg.Printf(_("In the currently active set, Code::Blocks does not know\n"
                         "the global compiler variable \"%s\".\n\n"
                         "Please define it."), varName.wx_str());
            if (errorMessages != nullptr)
                errorMessages->push_back(msg);
            m_ui->DisplayInfoWindow(_("Global Compiler Variables"), msg);

            std::set<wxString> ar = {varName};

            m_ui->OpenEditWindow(ar);
            Reload();
        }
    }
    return value;
}