Thanks Ben,

So, if I am not selling the source of my library, all I need to do is to
send the developer(s) the PRC file and the ONLY header file which defines
the interface to my library (the declaration of the function that can be
called from outside the library).

The developer just needs to install the PRC file on the device, include the
header fine in his/her project and he/she is good to go right!

Ben, is sending the PRC file secure enough? I just wanna make sure that my
code in the library is secure that way!

Please reply and correct me if I am wrong somewhere!
Thanks again,
Keyur.




-----Original Message-----
From: Ben Combee [mailto:[EMAIL PROTECTED] 
Sent: Thursday, July 22, 2004 5:03 PM
To: Palm Developer Forum
Subject: Re: Distibuting Library!

At 03:55 PM 7/22/2004, you wrote:
>Hi guys,
>
>I have got a kind of silly question!
>
>The thing is that I have developed a shared library project (consisting of
>several .c files and .h files). Now I want to distribute it/ sell it to
>other developers so that they can use the functionalities defined in my
>library.
>
>To test my library, what I am doing is, including the .mcp file of my
shared
>library project to the "Library" section of my application which then makes
>call to the function defined in the library.
>
>My question is, what am I supposed to send to the developer(s) in the form
>of library?

You'll need to send the PRC file for the library, and the header file that 
defines the interface to the library.  The other parts are private to the 
library, and only need be included if you're also distributing source.


-- Ben Combee, DTS technical lead, PalmSource, Inc.
    "Combee on Palm OS" weblog: http://palmos.combee.net/
    Palm OS Dev Fourm Archives: http://news.palmos.com/read/all_forums/



-- 
For information on using the Palm Developer Forums, or to unsubscribe,
please see http://www.palmos.com/dev/support/forums/



-- 
For information on using the Palm Developer Forums, or to unsubscribe, please see 
http://www.palmos.com/dev/support/forums/

Reply via email to