Generate should be called after the first Build

[GoogleCodeExporter]

The Generate.bat script should be called after the very first build for two
reasons
1)grammar.y looks for ../gstconfig.h (gstreamer/gst/gstconfig.h) which is
copied by the script to gstreamer/gst 
2)The script generates some files needed to compile the Python bindings.

I think adding a step in the root Readme.txt is enough

5. PyGobject (2.14)
       a. Download from
http://ftp.gnome.org/pub/GNOME/binaries/win32/pygobject/2.14/
6. Run ossbuild/Main/GStreamer/Generated.bat

What do you think? 

Original issue reported on code.google.com by ylatuya on 16 Jun 2009 at 12:54

[GoogleCodeExporter]

Why does it need to be called at all except when there are changes to the gst 
source 
that require it? 

The generated files are already in the repo, so the typical developer wouldn't 
need 
to run generate.bat at all b/c they're already there upon checkout. We might 
want to 
add a readme or something that describes what it does, though.

Original comment by david.g.hoyt on 8 Jul 2009 at 8:01

[GoogleCodeExporter]

There are some files like gstconfig.h that need to be copied to the sources 
folder.
As we don't want external files to pollute the original sources and putting 
them in
the 'Generated' folder wont work (grammar.c includes gstconfig.h using a 
relative
path), the only way to get these files in the sources folder is by running the
Generated.bat script. 
If you check out OSSBuild for the first time, gstconfig.h wont be copied to
gstreamer/gst unless you run Generate.bat. The same happens for the generated 
Python
bindings source.
You can reproduce it by deleting gstreamer/gst/gstconfig.h, which is unversioned
because it doesn't belong to original sources tarball. You will see that the
compilation fails because grammar.c doesn't find it.

Original comment by ylatuya on 8 Jul 2009 at 10:17

[GoogleCodeExporter]

You should be able to achieve this through using a forced include on only the 
files 
that require it. Or by adding an include path for the project or the properties 
file. Visual C++ will look in the default include path even for #include "..." 
declarations. The projects are outside the source folder and so would not 
pollute it.

Original comment by david.g.hoyt on 9 Jul 2009 at 10:41

[GoogleCodeExporter]

Done, isn't it?

Original comment by ylatuya on 11 Jul 2009 at 5:12

• Changed state: Done

[GoogleCodeExporter]

This is what I was talking about:
http://forja.rediris.es/forum/message.php?msg_id=133960

Original comment by ylatuya on 18 Jul 2009 at 10:44

[GoogleCodeExporter]

I saw the post - but I haven't made any changes. My computer's been under the 
weather as of late and I'm just now getting it back up and running (after 
putting in 
a new motherboard and new RAM).

Did you try using the forced include or include path?

Original comment by david.g.hoyt on 21 Jul 2009 at 1:20

[GoogleCodeExporter]

This is fixed in SVN r314: http://code.google.com/p/ossbuild/source/detail?r=314

Original comment by david.g.hoyt on 22 Jul 2009 at 8:57

[GoogleCodeExporter]

Great!

Original comment by ylatuya on 26 Jul 2009 at 6:28