[Buildroot] Project specific packages

[Buildroot] Project specific packages

[Ruud Commandeur]

Hi there,

I'm trying to add some project specific packages, as described in
"Using-buildroot-real-project". Just as described, I created a <company>
folder and within that folder a <test-app> folder, with the required
Config.in and .mk files. Also adjusted the Config.in to enable/disable
my test-app package.

However, if I do a "make test-app", I get:

make: *** No rule to make target `test-app'.  Stop.

I also tried a "make <company>", to force a make of all comapny
packages, with the same result. It seems that this only succeeds, if I
move the <test-app> folder to the root of the packages. But there goes
the idea of isolating all company specific packages in one directory.

Can anyone tell me how this should be done?

N.B. I hope I'm using the right mail-address for this kind of questions.
I also took a look at the mailing-list, but this seems to be more
development related and not so much for user questions. Please let me
know if I should a different address for posting my (future) questions.

Regards,

Ruud

[Buildroot] Project specific packages

[Thomas Petazzoni]

Dear Ruud Commandeur,

On Mon, 18 Mar 2013 12:14:26 +0100, Ruud Commandeur wrote:

> I'm trying to add some project specific packages, as described in
> "Using-buildroot-real-project". Just as described, I created a <company>
> folder and within that folder a <test-app> folder, with the required
> Config.in and .mk files. Also adjusted the Config.in to enable/disable
> my test-app package.
> 
> However, if I do a "make test-app", I get:
> 
> make: *** No rule to make target `test-app'.  Stop.
> 
> I also tried a "make <company>", to force a make of all comapny
> packages, with the same result. It seems that this only succeeds, if I
> move the <test-app> folder to the root of the packages. But there goes
> the idea of isolating all company specific packages in one directory.
> 
> Can anyone tell me how this should be done?

Could you post the patch containing the changes you have done? In
principle, what you've done looks good, but the devil is in the details.

> N.B. I hope I'm using the right mail-address for this kind of questions.
> I also took a look at the mailing-list, but this seems to be more
> development related and not so much for user questions. Please let me
> know if I should a different address for posting my (future) questions.

You're on the right mailing list!

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com