ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am a newbie in autoconf and automake.
After doing make I have the following questions?
How can I see that the build is with debug information?
What shall I do to build the release version?
Can I have the release version in one directory and the debug version in another? I mean, when I change from debug to release, make will not overwrite the debug version.
a question?
why are you running the auto tools one at a time manually ?
instead of
./configure
make
make install
-- or --
autoreconf -i -v
./configure,...
a question?
why are you running the auto tools one at a time manually ?
instead of
./configure
make
make install
-- or --
autoreconf -i -v
./configure,...
and what is it you are building ?
I am developing and building my own project from the command line and naturally I wan't to build a debug version as well as a release version
I am doing as you write
./configure
make
I am not doing "make install" because that will place the compiled program in some unknown directory.
I will not do make install before the program has passed some tests. By the way you don't have to do ./configure every time you have modified a code like *.cpp or *.h
I am not doing "make install" because that will place the compiled program in some unknown directory.
the default from auto tools should be /usr/local or /usr
depending on how you are setting it up for configure you can pass -debug to gcc ,or in the configure.in
and do you have ALL the needed programs installed to build a debug version on what ever distro is is
you have not said .
Quote:
building my own project from the command line
personally i like to use eclipse or Anjuta IDE's for that
or even Emacs it is better than bash
personally i like to use eclipse or Anjuta IDE's for that
or even Emacs it is better than bash
To use an IDE to develop software is like cheating.
Never mind I am also using an IDE (Visual Studio) then I move the software to a linux debian server where I rebuild the aplication. I think I get a release version but I am not sure.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
