Hi Stefan,
thanks for your prompt reply.
Now that we are on the cmake side of things I had a couple of general
questions.
I have some time from the office now to work on the latest eq stuff and
try to see what it would require to rewrite from scratch this wrapper
that exists here since 2009 ( auuutss.. ) but this time based on the sequel.
In order to organize the project for local dev here, ideally I would
like to be able to keep the necessary libs ( EQ, CO, LB etc ) as
separate projects ( something like what the structure of eq and co used
to look back in the day.. :)
Is there a recommended workflow / structure to achieve something like
this or the usage of Buildyard is a prerequisite ??
Buildyard has worked fine for me some times and some times other not.
Right now what I found to work out of the box for me was to clone
Equalizer and make which then caused Buildyard to fetch the dependencies
and build everything but ideally I would like to avoid this and be able
to compile and link the projects individually..
So, is there a recommended way of achieving this and if not what would
be your suggestion ??
Thanks!
Petros
On 2014-05-05 18:54, Stefan Eilemann wrote:
Hi Petros,
On 5. May 2014, at 14:07, Petros.Kataras [via Software]
<[email protected]> wrote:
[updates on some projects]
What would be the recommended way to disable this mechanism ?
Use 'make Equalizer-make' target, which will not update source. It needs all
the projects configured, i.e., you have to run at least once 'make Equalizer'
beforehand.
HTH,
Stefan.
_______________________________________________
eq-dev mailing list
[email protected]
http://www.equalizergraphics.com/cgi-bin/mailman/listinfo/eq-dev
http://www.equalizergraphics.com
