All of lore.kernel.org
 help / color / mirror / Atom feed
From: Romain Naour <romain.naour@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Add gpm (general purpose mouse) server package
Date: Fri, 17 Jan 2014 00:17:03 +0100	[thread overview]
Message-ID: <52D8686F.1060704@openwide.fr> (raw)
In-Reply-To: <52D8300E.80008@free.fr>

Hi Julien,

Le 16/01/2014 20:16, Julien Boibessot a ?crit :
> Hello Romain,
>
> and thanks for the review !
>

You're welcome.

>> May I suggest you to test gpm package with different toolchain 
>> configuration ?
>>
>> It won't build in static case (BR2_PREFER_STATIC_LIB=y):
>> "i686-buildroot-linux-uclibc/bin/ld: attempted static link of dynamic 
>> object `lib/libgpm.so.2'
>> collect2: error: ld returned 1 exit status"
>
> When I send patches they have been tested on different ARM target with 
> mainly 2 uClibc configs ("default" and "with large file, threads and 
> Co"), but not the one you mentionned (static lib)... sorry :-(
> Have you other configs that could lead to compilation problems ?

It's common source of failure in autobuilder, especially with new packages.
I'm not sure about mmu less case (BR2_USE_MMU=n)...

>
>>
>> There is also some errors about missing gpm.h in these files: (wrong 
>> path)
>> display-buttons.c
>> display-coords.c
>> get-versions.c
>
> where do you see that error ? (for me these tools are compiling fine 
> and working on target)
I get these error when ncurses is missing (see below):
prog/display-buttons.c:39:57: fatal error: gpm.h: no such file or directory
compilation terminated.
prog/display-coords.c:40:57: fatal error: gpm.h: no such file or directory
compilation terminated.
prog/get-versions.c:25:57: fatal error: gpm.h: no such file or directory
compilation terminated.

I need to add "headers/" before gpm.h

There is an optional dependency on ncurses:
ifeq ($(BR2_PACKAGE_NCURSES),y)
GPM_DEPENDENCIES += ncurses
GPM_CONF_OPT += --with-curses
else
GPM_CONF_OPT += --without-curses
endif
>
>> ||
>> And It would be good to disable the doc installation on target.
>
> why ?
> /usr/share/info/ and /usr/share/man/ are cleaned by Buildroot before 
> generating root filesystem images.
> Am I wrong ?
Sorry your right, I was abused by my command line :
"make toolchain gpm" which doesn't run target-finalize.

But this script (/usr/share/emacs/site-lisp/t-mouse.el) remain on target
I'm not sure it is really useful.
You can remove it with:
GPM_CONF_OPT += ac_cv_path_emacs=no

Be careful with makeinfo, because some host don't have it and fail to 
build the documentation.
Normally you can disable makeinfo with:
GPM_CONF_OPT += ac_cv_path_MAKEINFO=no
But I get an error during install...

>
>>
>> Thank for your contribution (I was working on gpm package too ;-) )
>
> Is yours very different from mine ? I'm not against merging your work 
> and sharing the credits or vis et versa.
Thanks, I gave you all my notes :)

Best regards,
Romain Naour
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140117/d39b9318/attachment.html>

      reply	other threads:[~2014-01-16 23:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-15 17:27 [Buildroot] [PATCH] Add gpm (general purpose mouse) server package julien.boibessot at free.fr
2014-01-15 21:31 ` Romain Naour
2014-01-16 19:16   ` Julien Boibessot
2014-01-16 23:17     ` Romain Naour [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52D8686F.1060704@openwide.fr \
    --to=romain.naour@openwide.fr \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.