From: Darrell S. <da...@sc...> - 2005-08-17 11:50:37
|
Thanks Egon, that sounds like a good plan. The way I've been working is to load the generator into eclipse, have it generate the code, and then use python's build system to build everything. For that to work, though, the generator needs to put things in directories that match the include paths in the generated code. Maybe a way to handle it is to have an output mapper or something that would handle mapping certain types of files to particular directories. It could handle both providing an output location for source & header files, and it could also provide the include lines that are put into the generated code to include particular header files. Darrell PS: If you add me as a ccmtools developer and provide a branch for me to check things in on, I'll work to integrate my changes (over time). What I tried to do was to have a command like flag (--coda) which would turn on the extra generation I added, but I'm sure it needs to be cleaned up a bit since I was under time pressure and learned as I went... On Aug 17, 2005, at 2:55 AM, Egon Teiniker wrote: > Hey Darrell! > > Darrell Schiebel wrote: > >> Could you change the directories so that the path matches the >> namespace >> instead of the directory name, i.e. "CCM_Local/ MyModule/..." >> instead of >> "CCM_Local_MyModule_...". I find it very useful to have the >> gererated >> code match the include entries (since I don't use confix). >> > > Yes I will try, but I think there is no common source structure > that can > be built with and without confix. > As a solution, I could define a property in > ccmtools/etc/ccmtools.properties that forces either a confix like or a > regular source structure... |