Author Topic: [Proposal] Move the custom variables WX_SUFFIX... to global variables  (Read 3332 times)

Offline sodev

  • Almost regular
  • **
  • Posts: 175
Re: [Proposal] Move the custom variables WX_SUFFIX... to global variables
« Reply #15 on: September 12, 2018, 08:18:06 pm »
This question i also always ask myself when a fresh installation of CodeBlocks asks me to put something into cb_release_type :P.

Anyway i like having this in the global variables as well because CodeBlocks has so many project files, changing this is such a PITA. And no, i don't use that Project Options Plugin, it is not that intuitive to use plus in the dark days of the past some of these variables had a different name in a few projects.

But i might be a bit biased, i use a lot of these global variables to pull in external libraries into my projects without polluting the project files with machine dependent paths :).

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 11199
    • Travis build status
Re: [Proposal] Move the custom variables WX_SUFFIX... to global variables
« Reply #16 on: September 12, 2018, 08:21:50 pm »
In my opinion everybody doing something a bit more complex should reconsider if using something like cmake isn't a better option. C::B's build system can do a lot of things, but it is more limited compared to something like cmake...
(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 BlueHazzard

  • Developer
  • Lives here!
  • *****
  • Posts: 2062
Re: [Proposal] Move the custom variables WX_SUFFIX... to global variables
« Reply #17 on: September 12, 2018, 09:08:59 pm »
What happens when these variables are empty?
How do you know what to put in there for initial values if you're new users and just starting?

We have discussed this countless times on the top. The conclusion was, that at the moment the same thing is to do for the "wx30" variable and the "cb_release_type"...
 We should provide a proper README and INSTALL file...
I volunteer for all upcoming forum posts to answer them without any grumble

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 11199
    • Travis build status
Re: [Proposal] Move the custom variables WX_SUFFIX... to global variables
« Reply #18 on: September 13, 2018, 01:07:34 am »
Hehe, and when you're tired of answering posts and quit?
Or people just don't be bothered to even post a question after they are greeted with some messages on project open?

I think it will be better if we have some UI and project storage for defaults and/or note/hints/help strings for the global variables?
I'm not really sure how this is supposed to work, but we need something like better than the current dialog.

A good example for similar tools is cmake-gui. It lists (almost) all variables and allows the user to set/change them.
There are tooltips with hints/help which is provided by users.
(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!]

Online ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 5109
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
Re: [Proposal] Move the custom variables WX_SUFFIX... to global variables
« Reply #19 on: September 16, 2018, 12:58:22 am »
BlueHazzard's work is great!

Under Windows, we have cbp/workspace/bat files for wx3.0 and wx3.1 and also we have 32bit and 64bit, maybe soon we will have wx3.2. I think we should only have one kinds of such files.

About OBF's suggestion of the UI, yes, it should be improved, at least some hint strings in the C::B's global variable setting dialog.
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.