This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 168805 - Option to run custom-build-tool files before or after rest of compilation.
Summary: Option to run custom-build-tool files before or after rest of compilation.
Status: RESOLVED INCOMPLETE
Alias: None
Product: cnd
Classification: Unclassified
Component: Project (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Thomas Preisler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-20 12:42 UTC by blippblopp
Modified: 2009-07-21 11:37 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description blippblopp 2009-07-20 12:42:25 UTC
For custom files with custom build tool used to build them:

*There are many tools that uses a definition file to build source-code (code generators). This needs to be run _before_
the rest of the project is compiled since the source code outputs is then used in other source code files.
*It's also common with tools that messes around with the build result(executable), setting file properties, exe
compressors and such.

It would be very usable with a possibility to set a pre/post-compile flag for files with custom build tool to make sure
it's compiled before or after the rest of the project.

An alternative is some sort of priority, maybe 1->10 and all files added gets priority 5 as default. It can then be
changed by the user. Files with same priority can be compiled in any order. Lesser is compiled before, larger is
compiled after.
Comment 1 Thomas Preisler 2009-07-20 21:58:12 UTC
Have you looked at the LexYacc sample? Isn't that what you you are looking for?
Comment 2 blippblopp 2009-07-21 11:37:48 UTC
Thanks a lot for the hint. It looks similar to what I was looking for, yes.

My test set up looks like this:
somefile.protocol that I add as a file with a custom build tool (generate.exe). It builds somefile.h (no c or cpp) that
is then used by any source file in the project. somefile.protocol is set up as "outputs: somefile.h"

Checked the sample and it was setup in a similar way except that it has generated C files as well as header, it has a
manually added dependency (token.l<-y.tab.h) and it doesn't have additional ordinary C/cpp files having dependency
against the generated file.

In my case it doesn't work if the somefile.h is missing, it's not built. Got unable to find file somefile.h when the
source file that tries to include it is compiled.

However, when I manually added packets.h as an "Additional dependency" to the source file using it, it worked.
Is it correct that I need to manually add it as a dependency? Shouldn't the normal "#include" scanning take care of it?

The LexYacc example also has one manually added additional dependency, token.l has additional dependency to y.tab.h but
in this case there are no #include scanning however.

Either way it seems like a problem outside the netbeans IDE I guess.