GNOME.org
 

Re: [anjuta-list] anjuta-list Digest, Vol 50, Issue 5

Hi there,
thanks for your posts, I have recently started with GTK, Anjuta and Glade.
I have been a Linux CLI user for ages but not really a GUI person. I had some accidental success with Anjuta - meaning that when I downloaded it it worked (compiled a demo program successfully). It was on Xubuntu 86-64. I support some users on a 32 bit platform LMint 16 and 17 and it took me a while to get a 32bit build to work. This was, is , also due to some missing libraries. I have not solved the problem on the Linux Mint platform but I now build on a 32 Xubuntu platform which generates code that runs well on LM 16,17 (32bit).
The comments about the edit preferences were useful - I had not dug into them.
I have access to several small SATA HDD which I can use to hardware clone installations while I experiment.
In order to solve my library problems I tried 'pkg-config --list-all | sort | more' and so on. On one installation I installed glade which brought in many libraries which solved my gtk+ and glib missing etc problems.
I tried glade and anjuta on a Raspberry Pi and it works first time - like a charm, just a bit slower but hey great to have a go with. Sorry to tease but I don't have the numerical versions of my tests here but I am creating a matrix of my current versions versus success which I will post later. I felt so good about the Raspberry Pi anjuta platform that I gave a small talk to my local Raspberry Pi group...
Speaking about presentation, I found it interesting to run my small GTK test program ( makes two boxes ) and change the options (I found a useful document online giving the proper names of the layers used ). I wanted to see what the user could control outside my program - e.g. themes, roll-up option etc {more later}.
Thanks again for your posts - it feels good to get some comments and suggestions from this forum. 

Mike ( recently hooked on GTK+ )


On 13/12/14 23:00, anjuta-list-request gnome org wrote:

Send anjuta-list mailing list submissions to
        anjuta-list gnome org

To subscribe or unsubscribe via the World Wide Web, visit
        https://mail.gnome.org/mailman/listinfo/anjuta-list
or, via email, send a message with subject or body 'help' to
        anjuta-list-request gnome org

You can reach the person managing the list at
        anjuta-list-owner gnome org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of anjuta-list digest..."


Today's Topics:

    1. Re:  Adding and including libraries (John Coppens)
    2. Re:  Adding and including libraries (Fearsome)
    3. Re:  Adding and including libraries (S?bastien Granjoux)


----------------------------------------------------------------------

Message: 1
Date: Fri, 12 Dec 2014 11:54:48 -0300
From: John Coppens <john jcoppens com>
To: anjuta-list gnome org
Subject: Re: [anjuta-list] Adding and including libraries
Message-ID: <20141212115448 c9e169b00da50ff9cb79c887 jcoppens com>
Content-Type: text/plain; charset=US-ASCII

On Thu, 11 Dec 2014 23:47:55 +0100
Fearsome <fearsome green gmail com> wrote:

This has been (and still is at times), a cause for confusion for me too.


Add Library, New Library, and then selected gnet

Note that 'selected gnet' means you have to be careful to actually

- activate the checkbutton (the checkmark),
- click 'Add'
- then click 'Add' again.

After that, when recompiling, Anjuta should automatically (re)configure.

I've had a series of problems with Anjuta lately, which I haven't really
had time to debug. It seems that in some cases, the added library
is not added correctly in the src/Makefile.am file. The new library
is inserted in the wrong place, and I had correct that file manually.
This happened in my Anjuta, and in several machines of my students
(different versions)...


To be sure the paths are included correctly, do a

make V=1

in the root directory of your project. That way, the CC ... will be
replaced by the full gcc command and print
the complete compilation command and you'll be able to see if the path
from the .pc is included or not.

Please paste that output in a message (and maybe the src/Makefile.am)

John


------------------------------

Message: 2
Date: Fri, 12 Dec 2014 20:52:27 +0100
From: Fearsome <fearsome green gmail com>
Cc: anjuta-list gnome org
Subject: Re: [anjuta-list] Adding and including libraries
Message-ID:
        <CA+3QYOJ7vcmXGdMpkj2Ch9vjS1brXRmC-nEV0eeXKzWZER+B1A mail gmail com>
Content-Type: text/plain; charset="utf-8"

Doing

- activate the checkbutton (the checkmark),
- click 'Add'
- then click 'Add' again.

chrashes Anjuta. So does pressing "Add" without first doing "New
Library..." in the "Add Library" dialog.

Checked src/Makefile.am and there's no sight of gnet. I've attached it.

Running

make V=1

also does not show any sign of gnet. I've attached the output
(comp_out.txt).

I've also tried regenerating the project. This produced some output which
I've also attached (regen.txt). Here gnet seems to be found, however.

/Fred

On Fri, Dec 12, 2014 at 3:54 PM, John Coppens <john jcoppens com> wrote:


On Thu, 11 Dec 2014 23:47:55 +0100
Fearsome <fearsome green gmail com> wrote:

This has been (and still is at times), a cause for confusion for me too.


Add Library, New Library, and then selected gnet

Note that 'selected gnet' means you have to be careful to actually

- activate the checkbutton (the checkmark),
- click 'Add'
- then click 'Add' again.

After that, when recompiling, Anjuta should automatically (re)configure.

I've had a series of problems with Anjuta lately, which I haven't really
had time to debug. It seems that in some cases, the added library
is not added correctly in the src/Makefile.am file. The new library
is inserted in the wrong place, and I had correct that file manually.
This happened in my Anjuta, and in several machines of my students
(different versions)...


To be sure the paths are included correctly, do a

make V=1

in the root directory of your project. That way, the CC ... will be
replaced by the full gcc command and print
the complete compilation command and you'll be able to see if the path
from the .pc is included or not.

Please paste that output in a message (and maybe the src/Makefile.am)

John
_______________________________________________
anjuta-list mailing list
anjuta-list gnome org
https://mail.gnome.org/mailman/listinfo/anjuta-list


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.gnome.org/archives/anjuta-list/attachments/20141212/92b91c17/attachment.html>
-------------- next part --------------
make  all-recursive
make[1]: Entering directory '/home/fredrik/projects/gtkgettime'
Making all in src
make[2]: Entering directory '/home/fredrik/projects/gtkgettime/src'
gcc -DHAVE_CONFIG_H -I. -I..  -DPACKAGE_LOCALE_DIR=\""/usr/local/share/locale"\" -DPACKAGE_SRC_DIR=\"".. . "\" 
-DPACKAGE_DATA_DIR=\""/usr/local/share/gtkgettime"\" -pthread -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/mirclient 
-I/usr/include/mircommon -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo 
-I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include   -Wall -g -g -O2 -MT main.o -MD -MP -MF .deps/main.Tpo -c -o main.o main.c
Makefile:356: recipe for target 'main.o' failed
make[2]: Leaving directory '/home/fredrik/projects/gtkgettime/src'
Makefile:405: recipe for target 'all-recursive' failed
make[1]: Leaving directory '/home/fredrik/projects/gtkgettime'
Makefile:324: recipe for target 'all' failed
-------------- next part --------------
Building in directory: /home/fredrik/projects/gtkgettime
make distclean
Making distclean in src
make[1]: Entering directory '/home/fredrik/projects/gtkgettime/src'
make[1]: Entering directory '/home/fredrik/projects/gtkgettime/src'
test -z "gtkgettime" || rm -f gtkgettime
rm -f *.o
rm -f *.tab.c
test -z "" || rm -f
test . = "." || test -z "" || rm -f
rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
rm -rf ./.deps
rm -f Makefile
make[1]: Leaving directory '/home/fredrik/projects/gtkgettime/src'
make[1]: Leaving directory '/home/fredrik/projects/gtkgettime/src'
make[1]: Entering directory '/home/fredrik/projects/gtkgettime'
make[1]: Entering directory '/home/fredrik/projects/gtkgettime'
test -z "" || rm -f
test . = "." || test -z "" || rm -f
rm -f config.h stamp-h1
rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
rm -f cscope.out cscope.in.out cscope.po.out cscope.files
make[1]: Leaving directory '/home/fredrik/projects/gtkgettime'
make[1]: Leaving directory '/home/fredrik/projects/gtkgettime'
rm -f config.status config.cache config.log configure.lineno config.status.lineno
rm -f Makefile
Building in directory: /home/fredrik/projects/gtkgettime
/home/fredrik/projects/gtkgettime/autogen.sh --enable-maintainer-mode
processing /home/fredrik/projects/gtkgettime
Running aclocal  ...
Running autoheader...
Running automake --gnu  ...
/home/fredrik/projects/gtkgettime/src/Makefile.am:7: warning: gtk+-3.0_CFLAGS: non-POSIX variable name
/home/fredrik/projects/gtkgettime/src/Makefile.am:28: warning: gtk+-3.0_LIBS: non-POSIX variable name
Running autoconf ...
Running /home/fredrik/projects/gtkgettime/configure --enable-maintainer-mode ...
configure: WARNING: unrecognized options: --enable-maintainer-mode
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether make supports nested variables... (cached) yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for GNET... yes
checking for GTKGETTIME... yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating config.h
config.status: executing depfiles commands
configure: WARNING: unrecognized options: --enable-maintainer-mode
Now type `make' to compile.
Completed successfully
Total time taken: 2 secs
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Makefile.am
Type: application/octet-stream
Size: 485 bytes
Desc: not available
URL: <https://mail.gnome.org/archives/anjuta-list/attachments/20141212/92b91c17/attachment.obj>

------------------------------

Message: 3
Date: Sat, 13 Dec 2014 11:52:28 +0100
From: S?bastien Granjoux <seb sfo free fr>
To: Fearsome <fearsome green gmail com>
Cc: anjuta-list gnome org
Subject: Re: [anjuta-list] Adding and including libraries
Message-ID: <548C1A6C 4050306 free fr>
Content-Type: text/plain; charset=windows-1252; format=flowed

Hi,


Le 12/12/2014 20:52, Fearsome a ?crit :

Doing
- activate the checkbutton (the checkmark),
- click 'Add'
- then click 'Add' again.
chrashes Anjuta. So does pressing "Add" without first doing "New
Library..." in the "Add Library" dialog.
Checked src/Makefile.am and there's no sight of gnet. I've attached it.

Adding a library needs 2 clicks because in autotools, libraries are
group so you need to create a new group and add the library in this
group. I have tried to make it simple but obviously I haven't completely
succeed.

The way it should work normally is the following:

- Select the target where you want to add the library, typically your
executable, in the project pane.
- Select Project->Add library
- The dialog display the currently selected target and the groups
already available.
- Let's consider that the new library is not available in any group, so
click on New Library button
- A dialog pop up, allowing you to create a new group. It already lists
all available libraries installed on your system.
- Select all libraries that you want to include in the group by clicking
in the checkbox in front of each library. By default it
will automatically create a group name. You can change it at the bottom
of the dialog.
- When you have selected all libraries and have a name for the group,
click on Add
- You should be back on the first dialog with a new group containing the
library you want.
- Check that the target is right, select this group and click Add
- It should add the new group to your target and update configure and
make files.


Regards,

S?bastien


------------------------------

Subject: Digest Footer

_______________________________________________
anjuta-list mailing list
anjuta-list gnome org
https://mail.gnome.org/mailman/listinfo/anjuta-list


------------------------------

End of anjuta-list Digest, Vol 50, Issue 5
******************************************
[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]