Re: Sharing code as headers or shared libraries
Take a look at the SampleLib example that ships with the SDK. If you want to ship a binary version of your code then this is probably the cleanest option. There are other ways to do what you're after but a shared library is prolly the best way to go. Good luck, Gavin. -- For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/
Re: Sharing code as headers or shared libraries
Thanks for the guidance, I'm looking into shared libraries now, but can someone elaborate on a "static library" ?? thanks Jim Stringer <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > > >Subject: Re: Sharing code as headers or shared libraries > >From: Gavin Maxwell <[EMAIL PROTECTED]> > >Date: Tue, 31 Oct 2000 15:35:41 +1100 > > >Take a look at the SampleLib example that ships with the SDK. > > >If you want to ship a binary version of your code then this is probably the > >cleanest option. There are other ways to do what you're after but a shared > >library is prolly the best way to go. > > >Good luck, > > >Gavin. > > Actually, from the description originally provided, it looks like a > static library would be a better alternative. > > Roger Stringer > Marietta Systems, Inc. > > > -- For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/
Re: Sharing code as headers or shared libraries
Thanks a bunch for the guidance, You right, it looks like the second choice would be best for what I am doing regards Jim Dave Johnson <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > > At 11:35 AM -0800 10/31/00, Dave Johnson wrote: > >At 1:04 PM -0500 10/31/00, Jim Duffy wrote: > >>I'm looking into shared libraries now, but can someone elaborate on a > >>"static library" ?? > > > > >Users of the library don't have to link any code into their > >projects: they just include a header, and write some code to find > >and open the library at runtime. The library can be dynamically > >loaded and unloaded as the programmer wishes. The library is a > >separate file that needs to be installed on the Palm, it's not > >automatically part of the application. > > Whoops, I forgot the word "shared" in the first sentence, it should read: > > "Users of a shared library don't have to link any code into their projects..." > > Dave Johnson > > -- For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/
Re: Sharing code as headers or shared libraries
Thanks a bunch for the guidance, You right, it looks like the second choice would be best for what I am doing regards Jim Dave Johnson <[EMAIL PROTECTED]> wrote in message news:28733@palm-dev-forum... > > At 11:35 AM -0800 10/31/00, Dave Johnson wrote: > >At 1:04 PM -0500 10/31/00, Jim Duffy wrote: > >>I'm looking into shared libraries now, but can someone elaborate on a > >>"static library" ?? > > > > >Users of the library don't have to link any code into their > >projects: they just include a header, and write some code to find > >and open the library at runtime. The library can be dynamically > >loaded and unloaded as the programmer wishes. The library is a > >separate file that needs to be installed on the Palm, it's not > >automatically part of the application. > > Whoops, I forgot the word "shared" in the first sentence, it should read: > > "Users of a shared library don't have to link any code into their projects..." > > Dave Johnson > > -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
Re: Sharing code as headers or shared libraries
On Tue, Oct 31, 2000 at 01:04:29PM -0500, Jim Duffy wrote: > > Thanks for the guidance, > > I'm looking into shared libraries now, but can someone elaborate on a > "static library" ?? static is the opposite of shared. You link your code with a static library, and it gets actual code included. A shared library will only include hooks to the shared library file. -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
Re: Sharing code as headers or shared libraries
At 11:35 AM -0800 10/31/00, Dave Johnson wrote: >At 1:04 PM -0500 10/31/00, Jim Duffy wrote: >>I'm looking into shared libraries now, but can someone elaborate on a >>"static library" ?? > >Users of the library don't have to link any code into their >projects: they just include a header, and write some code to find >and open the library at runtime. The library can be dynamically >loaded and unloaded as the programmer wishes. The library is a >separate file that needs to be installed on the Palm, it's not >automatically part of the application. Whoops, I forgot the word "shared" in the first sentence, it should read: "Users of a shared library don't have to link any code into their projects..." Dave Johnson -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
Re: Sharing code as headers or shared libraries
At 1:04 PM -0500 10/31/00, Jim Duffy wrote: >I'm looking into shared libraries now, but can someone elaborate on a >"static library" ?? Users of the library don't have to link any code into their projects: they just include a header, and write some code to find and open the library at runtime. The library can be dynamically loaded and unloaded as the programmer wishes. The library is a separate file that needs to be installed on the Palm, it's not automatically part of the application. A static library is just a compiled version of your code in a binary file. A programmer would add that file to their project (just like we all add runtime Palm libraries to our projects), include the header file where it's needed, and just call the code, like any other routine in the project. No need to find and open the library, it's already there as part of their code. And no need to install it on the Palm as a separate file. In your case, it seem like the latter may be more appropriate. You'd distribute the header file and a small binary file that other programmers would link into their projects. Dave Johnson -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
Re: Sharing code as headers or shared libraries
Thanks for the guidance, I'm looking into shared libraries now, but can someone elaborate on a "static library" ?? thanks Jim Stringer <[EMAIL PROTECTED]> wrote in message news:28659@palm-dev-forum... > > >Subject: Re: Sharing code as headers or shared libraries > >From: Gavin Maxwell <[EMAIL PROTECTED]> > >Date: Tue, 31 Oct 2000 15:35:41 +1100 > > >Take a look at the SampleLib example that ships with the SDK. > > >If you want to ship a binary version of your code then this is probably the > >cleanest option. There are other ways to do what you're after but a shared > >library is prolly the best way to go. > > >Good luck, > > >Gavin. > > Actually, from the description originally provided, it looks like a > static library would be a better alternative. > > Roger Stringer > Marietta Systems, Inc. > > > -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
Re: Sharing code as headers or shared libraries
Take a look at the SampleLib example that ships with the SDK. If you want to ship a binary version of your code then this is probably the cleanest option. There are other ways to do what you're after but a shared library is prolly the best way to go. Good luck, Gavin. -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
