genivi-ipc@lists.genivi.org

Development list for inter process communication (IPC) related topics

View all threads

Re: [Genivi-ipc] Guide to build Common API deprecated version (2.1.4)

윤승현
Tue, May 15, 2018 1:15 PM

Hello,

I might be thinking too simple, and it may be something you already know,
but before you cmake to explicitly link the patched libdbus,

you can set the package search priority by using the following command:

If patched libdbus is installed in /usr/local/lib,

export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig:$PKG_CONFIG_PATH

I hope this helps

Best Regards,

SeungHyun Yun

------------Original Message------------

Subject : Re: [Genivi-ipc] Guide to build Common API deprecated version
(214)

Date : 2018-05-15 00:15:23

From : Gunnar Andersson <gandersson@geniviorg>

To : Suraj Kottayi <surajkottayi@tcscom>

Cc : Ramya Saraswathi <RamyaSaraswathi@tcscom>, Tammanna S
<tammannas@tcscom>, Rabindra Nayak <rabindranayak@tcscom>,
genivi-ipc@listsgeniviorg, JFoster@luxoftcom

By the way, could you remind me why you say 3110 is the recommended
version? From what I can see there are newer versions also, and
3110 looks like it's around 15 years old

Thanks,

  • Gunnar

On Mon, 2018-05-14 at 18:07 +0530, Suraj Kottayi wrote:
> Hi ,
>
> We used the genivi recommended version of common-api tools (v
> 3110) and had generated commonapi files out of fidl files However, we
> could not generate some of the cpp files like Browsercpp (which we had
> added manually from media-manager interfaces source code available in
> Github), is it alright to do so? In the cmake files we had to comment
> out the h files which were not generated by commonapi tools After these
> modifications we were able to generate the makefile successfully But at
> the last step of compilation (in the linking phase) we were getting an
> error called "libCommonAPI-Dbusso :undefined reference to
'some dbus
> methods' " Our question is since libCommonAPI-DBusso is
dependent on
> patched version of libdbus (from common api documentation) do we need
to
> specify the linkage explicitly ? If yes how do we link our code to the
> patched library of dbus provided our system already has a libdbus
> installed in it(unpatched library)?
>
> If possible can u arrange any help from the so called common api
> maintainer
>
> With Best Regards
> Suraj Kottayi
> Systems Engineer
> Tata Consultancy Services ,
> Emp Id : 1029321
> MobileNumber : 8086318292
> MailId : surajkottayi@tcscom
> Web site : wwwtcscom
>
>
> -----Gunnar Andersson <gandersson@geniviorg> wrote: -----
> To: Suraj Kottayi <surajkottayi@tcscom>
> From: Gunnar Andersson <gandersson@geniviorg>
> Date: 05/11/2018 07:52PM
> Cc: "genivi-ipc@listsgeniviorg"
<genivi-ipc@listsgeniviorg>, Tammanna
> S <tammannas@tcscom>, Prasanna Seshadri
<prasannaseshadri@tcscom>, "ge
> nivi-projects@listsgeniviorg"
<genivi-projects@listsgeniviorg>, Ramya
> Saraswathi <RamyaSaraswathi@tcscom>, Rabindra Nayak
<rabindranayak@tcs
> com>, K Manjunath3 <kmanjunath3@tcscom>, Madhu Chandrashekar
<madhuchan
> drashekar@tcscom>, "Foster, Jeremiah"
<JFoster@luxoftcom>
> Subject: Re: [Genivi-ipc] Guide to build Common API deprecated version
> (214)
>
> On Fri, 2018-05-11 at 12:59 +0530, Suraj Kottayi wrote:
> > Hi Foster,
> >
> > I have tried to update the common api to the latest version
> > (3110) However the common-api generation through fidl files
(Franca
> > IDL) are producing codes which are dependent on commonapi-core 214
>
> For
> > instance MediaTypeshpp ,a file generated from MediaTypesfidl is
>
> looking
> > for files like CommonPI/InputStreamh ,CommonAPI/typesh which are
not
> > available in common-api-core v3110


genivi-ipc mailing list
genivi-ipc@listsgeniviorg
https://listsgeniviorg/mailman/listinfo/genivi-ipc

Hello, I might be thinking too simple, and it may be something you already know, but before you cmake to explicitly link the patched libdbus, you can set the package search priority by using the following command: If patched libdbus is installed in /usr/local/lib, export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig:$PKG_CONFIG_PATH I hope this helps Best Regards, SeungHyun Yun ------------Original Message------------ Subject : Re: [Genivi-ipc] Guide to build Common API deprecated version (214) Date : 2018-05-15 00:15:23 From : Gunnar Andersson &lt;gandersson@geniviorg&gt; To : Suraj Kottayi &lt;surajkottayi@tcscom&gt; Cc : Ramya Saraswathi &lt;RamyaSaraswathi@tcscom&gt;, Tammanna S &lt;tammannas@tcscom&gt;, Rabindra Nayak &lt;rabindranayak@tcscom&gt;, genivi-ipc@listsgeniviorg, JFoster@luxoftcom By the way, could you remind me why you say 3110 is the recommended version? From what I can see there are newer versions also, and 3110 looks like it&#39;s around 15 years old Thanks, - Gunnar On Mon, 2018-05-14 at 18:07 +0530, Suraj Kottayi wrote: &gt; Hi , &gt; &gt; We used the genivi recommended version of common-api tools (v &gt; 3110) and had generated commonapi files out of fidl files However, we &gt; could not generate some of the cpp files like Browsercpp (which we had &gt; added manually from media-manager interfaces source code available in &gt; Github), is it alright to do so? In the cmake files we had to comment &gt; out the h files which were not generated by commonapi tools After these &gt; modifications we were able to generate the makefile successfully But at &gt; the last step of compilation (in the linking phase) we were getting an &gt; error called &quot;libCommonAPI-Dbusso :undefined reference to &#39;some dbus &gt; methods&#39; &quot; Our question is since libCommonAPI-DBusso is dependent on &gt; patched version of libdbus (from common api documentation) do we need to &gt; specify the linkage explicitly ? If yes how do we link our code to the &gt; patched library of dbus provided our system already has a libdbus &gt; installed in it(unpatched library)? &gt; &gt; If possible can u arrange any help from the so called common api &gt; maintainer &gt; &gt; With Best Regards &gt; Suraj Kottayi &gt; Systems Engineer &gt; Tata Consultancy Services , &gt; Emp Id : 1029321 &gt; MobileNumber : 8086318292 &gt; MailId : surajkottayi@tcscom &gt; Web site : wwwtcscom &gt; &gt; &gt; -----Gunnar Andersson &lt;gandersson@geniviorg&gt; wrote: ----- &gt; To: Suraj Kottayi &lt;surajkottayi@tcscom&gt; &gt; From: Gunnar Andersson &lt;gandersson@geniviorg&gt; &gt; Date: 05/11/2018 07:52PM &gt; Cc: &quot;genivi-ipc@listsgeniviorg&quot; &lt;genivi-ipc@listsgeniviorg&gt;, Tammanna &gt; S &lt;tammannas@tcscom&gt;, Prasanna Seshadri &lt;prasannaseshadri@tcscom&gt;, &quot;ge &gt; nivi-projects@listsgeniviorg&quot; &lt;genivi-projects@listsgeniviorg&gt;, Ramya &gt; Saraswathi &lt;RamyaSaraswathi@tcscom&gt;, Rabindra Nayak &lt;rabindranayak@tcs &gt; com&gt;, K Manjunath3 &lt;kmanjunath3@tcscom&gt;, Madhu Chandrashekar &lt;madhuchan &gt; drashekar@tcscom&gt;, &quot;Foster, Jeremiah&quot; &lt;JFoster@luxoftcom&gt; &gt; Subject: Re: [Genivi-ipc] Guide to build Common API deprecated version &gt; (214) &gt; &gt; On Fri, 2018-05-11 at 12:59 +0530, Suraj Kottayi wrote: &gt; &gt; Hi Foster, &gt; &gt; &gt; &gt; I have tried to update the common api to the latest version &gt; &gt; (3110) However the common-api generation through fidl files (Franca &gt; &gt; IDL) are producing codes which are dependent on commonapi-core 214 &gt; &gt; For &gt; &gt; instance MediaTypeshpp ,a file generated from MediaTypesfidl is &gt; &gt; looking &gt; &gt; for files like CommonPI/InputStreamh ,CommonAPI/typesh which are not &gt; &gt; available in common-api-core v3110 _______________________________________________ genivi-ipc mailing list genivi-ipc@listsgeniviorg https://listsgeniviorg/mailman/listinfo/genivi-ipc