| Re: [translations] compiling error "make: Entering an unknown directory" |
[ Thread Index |
Date Index
| More lilynet.net/translations Archives
]
- To: Francisco Vila <paconet.org@xxxxxxxxx>
- Subject: Re: [translations] compiling error "make: Entering an unknown directory"
- From: Federico Bruni <fedelogy@xxxxxxxxx>
- Date: Sat, 07 Jan 2012 16:56:25 +0100
- Cc: Jean-Charles Malahieude <lilyfan@xxxxxxxxx>, LilyPond Translation <translations@xxxxxxxxxxx>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=ti618PihKpI5wwW8hMSeGsSk/2Z3T0QYPqYQEdJutsc=; b=X7r/h8RIPr4IdB1EcPKlTCWNeMupzJ9/2V/41VkLc8jYkx2ynh3XQQD1HZ50/WPP71 vIaCqUVpqo5FL7Cv19Y14YWMmKEz7PjdNmYzKa1heNpV5jGg25aSwSghmePgjxIxra+1 cgFmX+rCqmNQpgVLRB1fAI1SijcecvyaqZB6c=
Hi Francisco,
Il 06/01/2012 20:42, Francisco Vila ha scritto:
2012/1/4 Federico Bruni<fedelogy@xxxxxxxxx>:
> Il 03/01/2012 21:36, Federico Bruni ha scritto:
> I'm still curious to know how you build the doc.
> I would prefer using build/.... but maybe it is not recommended/allowed for
> translators?
I usually just 'make doc' and go shopping.
> Besides: I see no reason why a method in particular should be
> recommended specially for translators. Even less be disallowed.
I think that you didn't understand my question.
It is about *the directory where* you build lilypond.
In a previous email I better explained the issue (I've pasted it below).
Anyway, it doesn't really matter.
From now on I'll never build in build/
Il 03/01/2012 21:36, Federico Bruni ha scritto:
> BTW, how do you build Jean-Charles?
> In the root directory or in build/?
>
> I'm afraid that two builds could create conflicts...
> I used to:
>
> - first build lilypond in build/
>
> - then, in order to use the translation scripts, I need to run the
> configure in the root and then 'make -C scripts && make -C python'. This
> way I can cd into Documentation and run 'make check-translation'.
>
> There's any cons in this setup?
>
> For example, if I try a new build in build/ **after** running configure
> in the root directory, I get this warning:
>
> $ cd build
> $ ../configure
> ....
> ######################################################################
> Source directory already configured. Please clean the source directory
>
> make -C /home/fede/lilypond-git distclean
>
> and rerun configure.
> #######################################################################
>
> Then I can't run make:
>
> $ make
> make: *** No targets specified and no makefile found. Stop.
> fede@fede-laptop:~/lilypond-git/build$ ls
> config.hh config.log config.make config.status local.make
>
>
> Does it mean that translators shouldn't build in build/?
> Or I'm missing something?