How can I duplicate a build configuration ?

[dormky 5]

I have a build configuration that includes EurekaLog. Since EurekaLogs alone takes 15s of the build process I'd like a debug config where it's not enabled.

However I can't find anywhere in the IDE allowing me to duplicate a build configuration. You can export/import options, but not entire build configurations. Is that even something possible ?

[Lars Fosdal 1956]

Uncheck Base, Check Release - in the EL settings.

 

Personally I take the 15 secs, so that I can keep track of my leaks 😄

[dormky 5]

5 minutes ago, Lars Fosdal said:

Uncheck Base, Check Release - in the EL settings.

 

Personally I take the 15 secs, so that I can keep track of my leaks 😄

Unfortunately, we use the Debug build to compile releases (this is probably the least problematic thing about this project lol), but there's other things I want to change in the config, such as the output of warnings (guess what when you have thousands of warnings the time spent printing it to the debug channel adds up to a lot).

 

Also, we have so many leaks that it's not worth keeping track of at this point. More pressing things to do, somehow.

Edited February 2, 2024 by dormky

[Lars Fosdal 1956]

I assume you mean runtime warnings from custom code, and not thousands of compile time warnings?

You can create new build configs in the Project Explorer, and they also show up in the Eurekalog Config.



 

 

[dormky 5]

> I assume you mean runtime warnings from custom code, and not thousands of compile time warnings?

 

Nope, it's compile time warnings about string casts and the likes. Since a lot of the code is copy-pasted for each slightly different case, the warnings are too so there's really a lot of them ^^

 

The problem with creating a new configuration is that I lose the settings of the original config. We have things like a custom stack size, so I want to have the exact same config except for the Eurekalog flag and the warnings/hints.

 

I just figured I could edit the .proj directly to make sure the configs are the exact same and it seems to be fine 🙂

Edited February 2, 2024 by dormky

[dormky 5]

Ooooh I just realized you create the new config by right-clicking an existing one, not the "Build Configuration". Very cool, that works too and is much cleaner. Thanks !

[Lars Fosdal 1956]

np - I forgot to point out that little detail 

[Lars Fosdal 1956]

As for thousands of warnings ... Clean that mess up.  Warnings and even hints can relate to significant problems in the code.  If you have thousands that are "uninteresting", they still can drown out those that are really vital.

[klbass68 0]

On 2/2/2024 at 5:13 AM, dormky said:

Ooooh I just realized you create the new config by right-clicking an existing one, not the "Build Configuration". Very cool, that works too and is much cleaner. Thanks !

I just noticed this as well. However, the new one is created like a subfolder. 

[GabrielMoraru 56]

On 2/2/2024 at 12:17 PM, Lars Fosdal said:

As for thousands of warnings ... Clean that mess up.  Warnings and even hints can relate to significant problems in the code.  If you have thousands that are "uninteresting", they still can drown out those that are really vital.

@Lars - Man! You are too calm. By this time I would have already placed an order on Amazon for a couple of grenades to send them to the user 🙂 🙂 🙂 .
I have seen projects like this. Once the developers reach 100 warnings, they say that the shit has hit the fan and it is too much work ANYWAY to clean them up now.
Then they permanently close the Messages window and never look back.

 

__________

 

@dormky

You need to understand that most warnings translate (sooner or later) to bugs. And nobody likes a "crashy" program. If your program does not crash, please do a batch search and report back how many times the keyword "except" appears in your code.

 

This is why they say, "Treat your hints as waning and your warnings as errors!"
Take two days off, take a beer, go to the beach, and clean them up.

BUT for god's sake, don't hide them under the rug by manually forcing the compiler warnings off with compiler directives! Do the job properly. 

Start with the easy ones. You could easily fix the top 90% (easy ones) in one day. Leave the complex ones for the end. It won't be that frightening when you are left with only 20-30, even if those are the "heavy" ones (that require actual code refactoring).

_

For 3 of the most complicated ones, I will give you free advice (on this forum or on my blog). But I can put my hand into the fire that other forum participants will jump to help also.

Update: Maybe I can do some refactoring for you if your project meets the requirements of this "challenge".

Edited 23 hours ago by GabrielMoraru