NO

Author Topic: Global folder settings do not effect in compiler@linker execution parapms.  (Read 7714 times)

dizergin

  • Guest
Re: Global folder settings do not effect in compiler@linker execution parapms.
« Reply #15 on: October 16, 2014, 09:05:16 AM »
There is one problem with Project options and Folders.
If you clear those INCLUDE and LIB fields, those are copied from global ones and Macros INCLUDE and LIB macros stay empty :(

Those fields should stay as user wants as Default-button is there for filling those.
If we are talking of the common  practice (please look in my previous message) - the "default" button must reset (possibly wrong changed) settings to its defaults (=down to the point as the IDE was installed) values to ensure its (whole ide) flawless work without any reinstallation. At the moments it is just printing the value of the system path variable into the list box - that is whole shit (by the all means).
« Last Edit: October 16, 2014, 09:44:46 AM by dizergin »

Offline frankie

  • Global Moderator
  • Member
  • *****
  • Posts: 2113
Re: Global folder settings do not effect in compiler@linker execution parapms.
« Reply #16 on: October 16, 2014, 01:53:59 PM »
That functionality is  not unique to Pelles  IDE. EVERY industrial quality IDE  have it (and many of "homemade" IDE got it).
...
And the Pelles Help just declares that behavior formally.  So I can not see ANY reason why the Pelles IDE  must be different from the others at the point. And if you refuse the  feature in the normal existance and workflow (for whatever reasons)- it is much more honest just to reap out the feature wholly  and do not mess with any demagogy  or speculations.
Who said it is uniqe to PellesC?  ??? ???
The help simply describe the usage...  ???
"It is better to be hated for what you are than to be loved for what you are not." - Andre Gide

dizergin

  • Guest
Re: Global folder settings do not effect in compiler@linker execution parapms.
« Reply #17 on: October 16, 2014, 03:33:07 PM »
That functionality is  not unique to Pelles  IDE. EVERY industrial quality IDE  have it (and many of "homemade" IDE got it).
...
And the Pelles Help just declares that behavior formally.  So I can not see ANY reason why the Pelles IDE  must be different from the others at the point. And if you refuse the  feature in the normal existance and workflow (for whatever reasons)- it is much more honest just to reap out the feature wholly  and do not mess with any demagogy  or speculations.
Who said it is uniqe to PellesC?  ??? ???
The help simply describe the usage...  ???
  ::) ok, ok, nevermind....  it is ok...