Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » U++ TheIDE » U++ TheIDE: Compiling, Linking, Debugging of your packages » How BLITZ works?
Re: How BLITZ works? [message #692 is a reply to message #684] Wed, 25 January 2006 19:36 Go to previous messageGo to previous message
hojtsy is currently offline  hojtsy
Messages: 241
Registered: January 2006
Location: Budapest, Hungary
Experienced Member
Can you tell more about how to detect which files can be combined, and how to select the macros which should be undefined? Or is this described somewhere already? My first thought is that all macro definitions should be gathered from the cpp itself and undefined after each cpp included. I think that macro definitions from the #included files should not be undefined, because the headers are included only once anyway if they are protected with included guards, as they should be.
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Unix compilation fails
Next Topic: mingwm10.dll not needed?!
Goto Forum:
  


Current Time: Sun Aug 24 22:21:03 CEST 2025

Total time taken to generate the page: 0.06558 seconds