On 01.12.2015 02:22, Khem Raj wrote:
On Nov 30, 2015, at 3:15 PM, Dvorkin Dmitry wrote:
I know. But
it really does not require to have libX* in the system to successfully run
JDK+our software
We're using simple tar xvzf jdk-...tar.gz in all of our embedded systems, so I
know what I'm talkin
> On Nov 30, 2015, at 3:15 PM, Dvorkin Dmitry wrote:
>
> I know. But
> it really does not require to have libX* in the system to successfully run
> JDK+our software
> We're using simple tar xvzf jdk-...tar.gz in all of our embedded systems, so
> I know what I'm talking about, sorry.
you are w
I know. But
it really does not require to have libX* in the system to successfully
run JDK+our software
We're using simple tar xvzf jdk-...tar.gz in all of our embedded
systems, so I know what I'm talking about, sorry.
This feature blocks my efforts to have a well-designed system with
Poky/Yoct
> On Nov 30, 2015, at 2:42 PM, Dvorkin Dmitry wrote:
>
>
> I'm trying to include binary JDK into my linux image.
> just unpacking jdk-...tar.gz into recipe image and packing it into RPM (I'm
> using RPM as base of my distribution).
>
> after adding
> INSANE_SKIP_${PN} = "file-rdeps ldflags de
I'm trying to include binary JDK into my linux image.
just unpacking jdk-...tar.gz into recipe image and packing it into RPM
(I'm using RPM as base of my distribution).
after adding
INSANE_SKIP_${PN} = "file-rdeps ldflags dev-so build-deps"
into recipe I've got no errors or warning while build