Error you must have libtool installed anjuta

Русские Блоги

Примечания к изучению Linux (5) — Linux + Anjuta build C ++ среда разработки

1. Введение в Анюту

• Что такое Анюта
  Anjuta — это интегрированная среда разработки, созданная под GNU / Linux для обеспечения компиляции для C и C ++. Первоначально он был разработан для GTK / GNOME и имеет хорошие свойства программирования. Это включает в себя характер управления проектами, разработку приложений, интерактивную отладку, мощное редактирование кода и подсветку синтаксиса.

2. Тестовая платформа

• платформа тестирования
  Версия для Linux: Ubuntu 18.04 LTS

3. Установить Анюта

• 3.1 Авторизуйтесь в корневом аккаунте
  Чтобы обеспечить бесперебойную установку, сначала переключите учетную запись на корневую. Смотрите метод переключения:https://blog.csdn.net/u014337397/article/details/80874667
• 3.2 Установить Anjuta
  Введите команду:

После ввода команды для запуска установки вам необходимо ввести Y для подтверждения во время процесса установки. Скриншот после установки выглядит следующим образом:

3.3 Интерфейс программы

3.4 Возможные ошибки
При компиляции программы на C ++, если libtool не установлен, появится следующая ошибка:
Error: You must have `libtool’ installed
Решение:
выполните команду:

Источник

Anjuta

Contents

Anjuta-1.2.4

Anjuta officially supports wxWidgets (with some modifications, see below).

Anjuta-2.0.x

Currently in Alpha stage & not yet ready for regular use.

I installed Anjuta 2.0.2 on my Gentoo box, and tried to buld different projecs for wx. The executable worked out of the box. Steps to perform:

1. Create a new Anjuta project. Besides the «New» button, there is an arrow button. When you click on it, the list will appear. Choose «Project». 2. On the first Wizard page select the «C/C++» tab for the property page, and choose «wxWidgets». Click «Forward». 3. Fill out the form about the author and project name and version. Click «Forward». 4. If you want, change the location of the project and if the project should support internationalization. Leave everything else intact. Click «Forward». 5. Click «Apply». Anjuta will generate Makefiles. 6. Press «Shift+F11» to compile the project. (If you try to do a «Run» or «F3», you will get a message «Nothing to run!») 7. If the compilation successful, you can run and test you program.

However, if you want to build a DLL — either .so or .a — you will run into the problems. They were reported to the Anjuta team already, and hopefully will be fixed. As soon as I will have more info or the patch, I will update this page with the more info.

This is added by the oneeyeman on 08 September 2006 at 2:30 PM PDT.

if you try to compile the standard project template: First you need to add wxT() around «Hello World» on line 19 on the original template(main.cc): change «Hello World» to wxT(«Hello World»)

Disable overwriting of configure.in file: goto menu Project->Configure Project->Build Files and check «Project configure.in». Click ok.

Open configure.in (located at the root of your project dir) in your favourite text editor. Find the line «AM_PATH_WXCONFIG(2.3.2, wxWin=1)» and change the version to 2.6.2 (or whatever version you have). Now it should look somewhat like «AM_PATH_WXCONFIG(2.6.2, wxWin=1)»

Then you need to remove the else block of the if right below the line you just edited. That would be line 42 to 55 for me:

else
dnl Quick hack until wx-config does it
ac_save_LIBS=$LIBS
ac_save_CXXFLAGS=$CXXFLAGS
LIBS=$WX_LIBS
CXXFLAGS=$WX_CXXFLAGS
AC_LANG_SAVE
AC_LANG_CPLUSPLUS
AC_TRY_LINK([#include ],
[wxString test=»»],
,[WX_LIBS=$WX_LIBS_STATIC])
AC_LANG_RESTORE
LIBS=$ac_save_LIBS
CXXFLAGS=$ac_save_CXXFLAGS

CPPFLAGS=»$CPPFLAGS $WX_CPPFLAGS»
CXXFLAGS=»$CXXFLAGS $WX_CXXFLAGS_ONLY»
CFLAGS=»$CFLAGS $WX_CFLAGS_ONLY»

Now your configure.in should contain something like this:

AM_OPTIONS_WXCONFIG
AM_PATH_WXCONFIG(2.6.2, wxWin=1)
if test «$wxWin» != 1; then
AC_MSG_ERROR([
wxWindows must be installed on your system.

Please check that wx-config is in path, the directory
where wxWindows libraries are installed (returned by
‘wx-config —libs’ or ‘wx-config —static —libs’ command)
is in LD_LIBRARY_PATH or equivalent variable and
wxWindows version is 2.3.2 or above.
])
fi
CPPFLAGS=»$CPPFLAGS $WX_CPPFLAGS»
CXXFLAGS=»$CXXFLAGS $WX_CXXFLAGS_ONLY»
CFLAGS=»$CFLAGS $WX_CFLAGS_ONLY»

This small howto added by faern 09:35, 10 August 2006 (PDT). I wrote this just minutes after I found the solution, so it’s not well tested

Packages needed in (Ubuntu GNU/Linux)

If you install only the «Anjuta IDE» and try to create a wxWidgets application with the wizard, it can complain for missing some components. You can solve this by running the following command in a system console:

(done with a Ubuntu GNU/Linux 7.04 -64bit)

Источник

I try to install MapServer and have a problem with last command in tutorial:

Terminal says that cannot find command libtool / I went and installed libtool. But still command not work. I try:

And get an error:

What am I doing wrong?

OS:Mint. PS: First time see a Linux system.

2 Answers 2

Generally speaking, you as a normal user of the system do not work directly with libtool at all. Libtool is a convenience utility for software developers. You can see its effects, but if you ever have to «work with libtool » to get some software to build, it means something is broken. And then, you don’t so much work with libtool to fix it as attempt to fix the package’s build system. This may include replacing the copy of libtool you got with that package.

That’s the key thing you have to understand about Libtool: when you install it on your system, as you have done, you don’t get a libtool program to run. The main command you get is libtoolize , and its primary purpose is to generate the libtool script shipped with a source tarball.

So, this software you’re trying to build isn’t using the libtool command on the system, it’s using the one that came with the source tarball. About all you as a normal user can hope to try is replacing it by re-running libtoolize , but I wouldn’t recommend that as a general troubleshooting step. It has a pretty decent chance of breaking things rather than fixing them.

Источник

Anjuta Building

Building the latest version of Anjuta is quite difficult at the moment mainly if your distro hasn’t switched to Gtk 3.0 yet. Here is some, I hope, useful advices. First, check if your are able to install it using pre-build GNOME 3 dependencies as described at anjuta site. If not, you can use JHBuild as described below.

JHBuild

One of the easiest solutions is to use JHBuild. JHBuild is a powerful tool to build the GNOME stack. As all major distributions currently don’t ship the new GNOME 3.x libraries it is very difficult to build anjuta manually and jhbuild can be a great help.

JHBuild is included in the major distributions so please install with

Afterwards create a .jhbuildrc file in your home directory. You should use the file anjuta.jhbuildrc in anjuta project directory as template but be sure to adjust the paths. Details can be found in the JHbuild documentation.

• Build anjuta (whole stack, will rebuild everything)

• Build only anjuta module (should only be necessary if you need to run autogen.sh, otherwise you can just build anjuta as you did before)

• Build some parts of the stack

• Starting a shell in JHBuild environment

Without JHBuild

JHBuild is doing everything automatically: checking dependencies, downloading them and building all this with additional flags if needed. The drawback is that it rebuilds almost everything even if it is not necessary. You can compile yourself only the needed packages.

pkg-config

pkg-config is used by almost all configure script to find the right libraries. It is looking for a file named library_name.pc in /usr/lib/pkgconfig. This is a text file giving the version of the installed library and the needed dependencies. By default all programs and libraries are installed in /usr/local, so .pc files are installed in /usr/local/lib/pkgconfig but this directory is not checked. You need to define the environment variable PKG_CONFIG_PATH to add new directory by example:

GSettings schema

The new GSettings system used, in Gtk+3, need to find schemas files which are installed by default in /usr/local/share/glib-2.0/schemas when you install a program from sources. This directory is not checked by default. , so you need to define the environment variable GSETTINGS_SCHEMA_DIR, by example:

Libtool .la file

Most packages use libtool to find the dependencies needed by each library. These dependencies are stored in a file named libray_name.la in the same directory than the library.

The issue is that these files contains the absolute name of each dependency. If your program needs a new version of a library which is itself used by another system library, the linker will try to link with both versions of the library and will probably give an error.

One solution is to erase all .la files, they are not strictly necessary on Linux.

Another solution is to update all the .la files to make sure that all system libraries use the new version of the libraries if available. I have written a perl script here for doing this. You call it with the name of the directory where you have installed all local libraries typically /usr/local/lib, the script will find all libraries, get all dependencies and for all system dependencies it will copy the .la file from /usr/lib to /usr/local/lib and update the file to use the new libraries.

Apps/Anjuta/Building (last edited 2018-02-20 08:01:14 by SvitozarCherepii )

Источник

I try to install MapServer and have a problem with last command in tutorial:

Terminal says that cannot find command libtool / I went and installed libtool. But still command not work. I try:

And get an error:

What am I doing wrong?

OS:Mint. PS: First time see a Linux system.

2 Answers 2

Generally speaking, you as a normal user of the system do not work directly with libtool at all. Libtool is a convenience utility for software developers. You can see its effects, but if you ever have to «work with libtool » to get some software to build, it means something is broken. And then, you don’t so much work with libtool to fix it as attempt to fix the package’s build system. This may include replacing the copy of libtool you got with that package.

That’s the key thing you have to understand about Libtool: when you install it on your system, as you have done, you don’t get a libtool program to run. The main command you get is libtoolize , and its primary purpose is to generate the libtool script shipped with a source tarball.

So, this software you’re trying to build isn’t using the libtool command on the system, it’s using the one that came with the source tarball. About all you as a normal user can hope to try is replacing it by re-running libtoolize , but I wouldn’t recommend that as a general troubleshooting step. It has a pretty decent chance of breaking things rather than fixing them.

Источник

Страницы: [1]   Вниз

0 Пользователей и 1 Гость просматривают эту тему.

Страницы: [1]   Вверх

Report forwarded
to debian-bugs-dist@lists.debian.org, Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>:
Bug#771481; Package anjuta.
(Sun, 30 Nov 2014 02:24:06 GMT) (full text, mbox, link).

Acknowledgement sent
to Sascha Reißner <reiszner@novaplan.at>:
New Bug report received and forwarded. Copy sent to Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>.
(Sun, 30 Nov 2014 02:24:07 GMT) (full text, mbox, link).

Information forwarded
to debian-bugs-dist@lists.debian.org, Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>:
Bug#771481; Package anjuta.
(Tue, 13 Dec 2016 12:45:06 GMT) (full text, mbox, link).

Acknowledgement sent
to "Farkas, Joe" <Joe.Farkas@commscope.com>:
Extra info received and forwarded to list. Copy sent to Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>.
(Tue, 13 Dec 2016 12:45:06 GMT) (full text, mbox, link).