On Tue, Mar 23, 2010 at 10:06 PM, Tamas TEVESZ <[email protected]> wrote:
> On Tue, 23 Mar 2010, Carlos R. Mafra wrote:
>
>  > > this makes autoconf bend the way we need. i am not for a split second
>  > > claiming this is "right", but it works. seems to be ok on linux and
>  > > netbsd.
>  >
>  > Cool, I tested it here on linux and it works fine!
>
> good, good.
>
>  > > renato, can you test whether makes it unnecessary to manually patch
>  > > Makefile.am and screwing with platform CFLAGS on freebsd? (you still
>  > > wll have to apply the intl/gettext overrides)
>  >
>  > It would be nice to know the necessary steps on freebsd. Perhaps
>  > that could be made into a patch and make life easier to others.
>
> probably not. the only thing seems to be is that libintl for some
> reason is not picked up. i have just tested, that the bsd (citrus)
> libintl works fine (ok, links fine, and then i don't know and don't
> want to know how to see !english messages, but in any case, gettext is
> used for most everything, even if it doesn't have to snarf messages
> out of a po), it's just that it's not being picked up for some reason.
> i'll probably investigate that later.
>
> what might be beneficial though is to go through freebsd's patches and
> see if we can/want to use something.
>
> http://www.freebsd.org/cgi/cvsweb.cgi/ports/x11-wm/windowmaker/files/
>
> there are some items that look interesting.

You need to look at [1] too, specially on post-patch: target, when you can
see what we do with %%MACROS%% we substituted with patches. All
of these we needed to do to make wmaker respect ${PREFIX}, ${PERL} and
${LOCALBASE} vars.

Have it fixed on autotools stuffs would be great.

Just one more thing, when you run ./configure--help, --with-gnustepdir is
still listed as a valid option, but if you try to use, it shows a warning saying
it's invalid param.

[1] 
http://www.freebsd.org/cgi/cvsweb.cgi/ports/x11-wm/windowmaker/Makefile?rev=1.147;content-type=text%2Fplain

-- 
Renato Botelho


--
To unsubscribe, send mail to [email protected].

Reply via email to