[anjuta-devel] Add new target

[Igor Korot]

Hi,
I am successfully working with Anjuta building my application on one machine
against GTK+2.
My application contains one binary executable and couple of .so.
Everything is located inside one "Workspace". The project is also
located on GitHub.

Now, on another machine I set up an environment with GTK+3.
I grabbed my source code from the GitHub and also everything I need.

However all my Makefile files are referencing GTK+2. And so I thought
that I can just
add the build target instead of trying to recreate the project and
change the Makefiles accordingly for the .so libraries.

Now here is the question:
When I add the build target and change the Makefiles will I be able
to push my changes to GitHub?
Or I will have to keep them local, because the build target is available only
to one current target?

Thank you.

[Sébastien Granjoux]

Hi,

Post by Igor Korot
When I add the build target and change the Makefiles will I be able
to push my changes to GitHub?
Or I will have to keep them local, because the build target is available only
to one current target?

I don't understand what you want to do.

But being able to compile a project with Gtk+2 or Gtk+3 is not
completely obvious even if it can be done by selecting an option in the
configure script.


Regards,

Sébastien

[Igor Korot]

Sebastien,

Post by Sébastien Granjoux
Hi,

Post by Igor Korot
When I add the build target and change the Makefiles will I be able
to push my changes to GitHub?
Or I will have to keep them local, because the build target is available only
to one current target?

I don't understand what you want to do.
But being able to compile a project with Gtk+2 or Gtk+3 is not completely
obvious even if it can be done by selecting an option in the
configure script.

Compiling is OK.
What I don't understand is following:

When I create a project, add the source and header files and do the
build it will
generate configure and all necessary files to compile just one target.

When you add the dynamic-link library, you will need to set properties for the
newly added target in order for this target to compile. (This is not so obvious
but OK).

Now, you put all this into the Git/CVS/etc. So that you configure script and 2+
Makefiles are properly maintained.

So far so good.

Now you need to create a different build target altogether.

So when you add new build target - what happened? I will still have to do
"configure" and then "build", right? But then when you run "configure"
the Makefile
that waqqs made previously will be overwritten. Will the new build
target be added
to the resulting Makefile or the resulting Makefile will contain just
one target?

And what happens with the DLL Makefile? Will it contain 1 target or 2 targets?

Because if the new Makefile will have 1 build target then pushing the
changes into
the version control is not good, since in my situation on the second
machine I will
need to change it to reflect the build target of the machine #2.

Let me know if this is still unclear and I will try to explain it more.

Thank you.

Post by Sébastien Granjoux
Regards,
Sébastien