You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! Sorry for late reply. Unfortunately, cbp2make doesn't know how to import Code::Blocks config (yet), so the fastest way to introduce a custom compiler to cbp2make is to configure it manually either through command line or by direct editing of cbp2make XML config. You can first run cbp2make dry with --local and --config options and then edit the template. I know it's inconvenient, but I'm having just the same problem with it.
The problem with importing Code::Blocks config is that Code::Blocks stores almost everything in CDATA sections and not in regular XML tags and parameters and then since 1) TinyXml cannot provide an API for parsing and r/w contents of CDATA sections because it can't possibly know its format and 2) correct me if I'm wrong, but internal Code::Blocks config doesn't seem to be well documented; reverse engineering of that format including studying Code::Blocks sources has been postponed during active development. Maybe we should give it another try, it's a nice feature afterall, I'd like it being implemented.
Activity
mirai-computing commentedon Dec 15, 2022
Hi! Sorry for late reply. Unfortunately, cbp2make doesn't know how to import Code::Blocks config (yet), so the fastest way to introduce a custom compiler to cbp2make is to configure it manually either through command line or by direct editing of cbp2make XML config. You can first run cbp2make dry with --local and --config options and then edit the template. I know it's inconvenient, but I'm having just the same problem with it.
The problem with importing Code::Blocks config is that Code::Blocks stores almost everything in CDATA sections and not in regular XML tags and parameters and then since 1) TinyXml cannot provide an API for parsing and r/w contents of CDATA sections because it can't possibly know its format and 2) correct me if I'm wrong, but internal Code::Blocks config doesn't seem to be well documented; reverse engineering of that format including studying Code::Blocks sources has been postponed during active development. Maybe we should give it another try, it's a nice feature afterall, I'd like it being implemented.