Re: Grumble...
On Aug 7, 2:34 am, =D6=F6 Tiib <oot...@hot.ee> wrote:
On 6 aug, 23:43, Sousuke <s0s...@gmail.com> wrote:
On Aug 6, 11:06 am, James Kanze <james.ka...@gmail.com> wrote:
On Aug 6, 12:53 pm, "Balog Pal" <p...@lib.hu> wrote:
[...]
Maybe the reason is that you're unaware of the alternative,
better ways to do things. For example, I've recently seen
talks in this group about makefiles. How about just letting
the IDE's project system do all the build tasks
automatically for you?
Just for the record, Visual Studios 2005 (the version we use
officially) does NOT handle all of the dependencies correctly.
We've had to impose a rule that in certain cases, you must click
on build twice, because the first build will ignore the
dependencies generated by the pre-build step.
Maybe you are unaware of *ALL* the build tasks that need to be
done. Perl is one way how to make it possible.
Or Python (I suspect). In my case, I learned all this before
there was perl or python, so I use the Bourne shell and the Unix
tool kit. We have imposed perl on all of our development
machines, however, and scripts I export, I have to rewrite in
perl.
Lets for example say that you have third party code generator
that generates 5% of the C++ code in project using .foo files
and .h files. Do you know how to add such .foo files to VS
2010 build system in a way that each time .foo file (or
dependant .h file) is changed it does rerun that code
generator for incremental build?
Ok, lets say that above-described code generator generates
code mostly OK, but does not take some peculiarity of
microsoft into account (some posix function was prefixed with
underline by MS). Now you obviously write a little script that
both calls that code-generator and afterprocesses the produced
code so underlines are added where needed.
Can you write such program as batch file? No? So what you do?
I think that you can use Visual Basic. And there is a command
line interpretor under Windows which you can (and we do) use,
including in actions in the pre-build and post-build steps. The
command line interpretor is pretty weak, but it is sufficient
for invoking an external tool, and passing its output through
sed. (Of course, you don't have sed, or anything like it.)
--
James Kanze