Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
event sequence question?
AndrewCot:
The display events plugin loads using the cbp attached to the post above. I now have the Linux workspace building in about 6 minutes instead of 189 after changing the -wall to -w as there are a HUGE number of warning that slow the build down due to the amount of text that needs to be processed due to the warnings.
Miguel Gimenez:
Added in r12658, thank you.
AndrewCot:
I am also not an autotools expert, but you have the following line:
--- Code: ---dsplayevents_default="yes"
--- End code ---
This would cause the plugin to be built by default, but I thought you did not want it built by default.
IMHO The Windows and Unix builds should be in sync with regards to building it by default or not. Either way a change is needed. I will deal with the unix project files as part of ticket 1175 once the decision is made for the default to build or not.
AndrewCot:
@Miguel I am merging the code into my local source tree and spotted that there are issues with indention differences with the change in the src\plugins\Makefile.am where your changes use space, but the rest of the file uses tabs. I have not checked the other files.As there is no a ticket for this change I am including my feedback in this thread. If there was a ticket (I am assuming there is not a ticket) I would include the feedback in the ticket. There needs to be a way of giving feedback to changes that do not have a ticket, but I have no idea how this could be done easily or how to do this on SF SVN repo's.
killerbot:
--- Quote from: AndrewCot on January 16, 2022, 11:51:02 am ---The display events plugin loads using the cbp attached to the post above. I now have the Linux workspace building in about 6 minutes instead of 189 after changing the -wall to -w as there are a HUGE number of warning that slow the build down due to the amount of text that needs to be processed due to the warnings.
--- End quote ---
I think the better solution, is to fix those warnings, and worst case pragma them out.
Note : for gcc, certain include paths can be silenced easily (eg wx) instead of -I<include_path> ==> -isystem<include_path>
That way we can focus on out own code and ignore the ones beyond out control.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version