Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Proposed Rules and suggestions for using PCH properly under Windows
stahta01:
--- Quote from: BlueHazzard on May 31, 2014, 10:49:30 am ---What are you trying to do with the scripted wizzard?
--- End quote ---
Trying to get it to make good PCH compatible code.
Edit: This means moving and reordering includes of headers, adding forward declares, and adding include of sdk.h
1. Fix Plugin code using PCH correctly by adding use of sdk.h in cpp files of ScripedWizard.
2. rebuild wxCode generated by (wxSmith) Edit: This step resulted in no changes to the code.
3. rebuild wxCode using PCH headers (InternalHeadersPCH and HeadersPCH)
4. Fix wxWidget code templates
5. Fix CB Plugin code templates
6. Fix CB Plugin wizard creation of CB Project (add sdk.h.gch search folder)
Not part of planned fixes in this branch at this time.
7. Rewrite CB Plugin wizard script to add non-pch target
Tim S.
stahta01:
--- Quote from: stahta01 on May 31, 2014, 03:01:30 pm ---
Not part of planned fixes in this branch at this time.
7. Rewrite CB Plugin wizard script to add non-pch target
--- End quote ---
7A. Fix building of two target of debug and release when using local PCH File.
7A1. Make location of local PCH file in object folder.
Tim S.
stahta01:
To oBFusCATed: These two changes needs to tested for build issues on a Linux box.
I have push out my local changes to my https://github.com/stahta01/codeblocks_sf_tims/tree/scriptedwizard
These items 1 and 3 should NOT cause any functional change in the plugin; but, might cause compile errors because of missing include.
I have tested on windows 7 32 bit using wxWidgets 2.8.12 and found no build problems.
Note: I used the wxSmith from CB version 13.12 to generated the wxSmith code.
--- Quote ---1. Fix Plugin code using PCH correctly by adding use of sdk.h in cpp files of ScripedWizard.
2. rebuild wxCode generated by (wxSmith) Edit: This step resulted in no changes to the code.
3. rebuild wxCode using PCH headers (InternalHeadersPCH and HeadersPCH)
--- End quote ---
Tim S.
oBFusCATed:
I'm testing this, then. Should I commit it to trunk if it doesn't fail?
btw: Don't use git merge operations, but only git rebase, because git's merge commits are incompatible with svn's.
stahta01:
--- Quote from: oBFusCATed on June 01, 2014, 10:45:56 am ---I'm testing this, then. Should I commit it to trunk if it doesn't fail?
btw: Don't use git merge operations, but only git rebase, because git's merge commits are incompatible with svn's.
--- End quote ---
Yes, please commit to svn trunk if it compiles on Linux using CB Project and configure/make.
Edit: Found out what rebase means http://git-scm.com/book/en/Git-Branching-Rebasing and http://git-scm.com/docs/git-rebase.html
Will try to do it that way in the future. I am using TortoiseGit; so, I really not sure how to use all of Git.
But, it shows a rebase command.
Tim S.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version