Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development

Project Exporter Plugin

<< < (3/4) > >>

ollydbg:
Once I know that gcc can generate a include files dependency. see:
c++ - Tool to track #include dependencies - Stack Overflow

and:

2.7 Automatic Dependency Generation

oBFusCATed:
I think that depslib does this, check the source it is in svn.

Alpha:
Thank you both; I will look to see which option fits my needs.

(By the way, I just managed to compile Code::Blocks with a makefile generated from a Bakefile exported by this plugin :).)

Alpha:
Should the Autotools section of this plugin be dependent on autoscan?
Autoscan already has many of rules for determining which macros should be included.  I am not sure if it would be wise for me to spend a lot of time to attempt to replicate this functionality.

I am considering having this plugin set up everything except for the detection macros autoscan produces; for these, it would read the configure.scan, if it is available, and insert them in the relevant parts.  (The files would still be created if there was no configure.scan, however they would contain a message warning that the user must run autoscan first if they want additional detection macros.)

ollydbg:

--- Quote from: Alpha on November 20, 2011, 08:37:34 pm ---Thank you both; I will look to see which option fits my needs.

(By the way, I just managed to compile Code::Blocks with a makefile generated from a Bakefile exported by this plugin :).)

--- End quote ---

I just see some other good tools:
include-what-you-use

--- Quote ---include-what-you-use is a tool to ensure that a file directly #includes all .h files that provide a symbol that the file uses. It also removes superfluous #includes from source files.
--- End quote ---

In the LLVM 3.0 Release Notes page.

Navigation

[0] Message Index

[#] Next page

[*] Previous page