[Developers] FW: myxomatosis example

[Johnoel Ancheta]

I may have a easy solution, but will need to test.  It involves creating 
a contrib.lib and contrib.h that
gets built with admb.  Easier for the end user...

On 8/2/11 10:48 AM, Mark Maunder wrote:
> John,
>
> I thought that the idea was to have the contributed code compiled in the libraries, but not include the #include statement somewhere so that the user had to physically put the include statement in their tpl (similar to how an R user has to physically load the library). The messy part is having to use the whole path to the code and not just the name of the library
>
> Mark
>
> -----Original Message-----
> From: developers-bounces at admb-project.org [mailto:developers-bounces at admb-project.org] On Behalf Of John Sibert
> Sent: Tuesday, August 02, 2011 1:41 PM
> To: developers at admb-project.org
> Subject: Re: [Developers] FW: myxomatosis example
>
> Well including stuff in the GLOBALS_SECTION does not seem particularly messy, Dave is correct the usual way is with a header file and a library.
>
> The practical question is how are the libraries assembled? Each OS/architecture/compiler combination brings unique problems. That is why we have the buildbot for the ADMB code. It might be feasible to include the contributed contribted code, but in my opinion the ADMB Project should not be responsible for maintenance of user-contributed code.
> Could we ask code contributors to create an appropriate header file and a makefile to create a library for their code? If so then users of the contributed code would have the option of either including the source code in the tpl or customizing the makefile to build libraries appropriate to their system.
>
> John
>
> On 08/01/2011 02:08 PM, dave fournier wrote:
>> On 11-08-01 04:15 PM, Mark Maunder wrote:
>>
>> The usual way is to include a header file and then to link in a
>> library with the compiled code.
>>
>>> Can anyone give advice on how to include user contributed libraries
>>> in the Globals section. This looks too messy. Can't you just do
>>> "#include ecolib"
>>>
>>> Thanks,
>>>
>>> Mark
>>>
>>> *From:*Mollie Brooks [mailto:mbrooks at ufl.edu]
>>> *Sent:* Monday, August 01, 2011 4:03 PM
>>> *To:* Mark Maunder
>>> *Subject:* myxomatosis example
>>>
>>> Hi Mark,
>>>
>>> I did an example from Ben's book. I'm also working on another one.
>>> This one requires a vectorized version of the dgamma function which I
>>> just added to Steve's statlib on the svn. I'd like any suggestions
>>> you might have, especially on the globals section. I think the
>>> developers should have a talk about making it as easy as possible for
>>> users to include libraries from the contrib directory. Maybe these
>>> should get moved to the include directory automatically when we
>>> compile. Also, the library pow_vectorized_RE should probably be
>>> incorporated into the core source.
>>>
>>> I did it using R2admb which currently doesn't work for windows, but
>>> I'm hoping Ben will have it working later this month.
>>>
>>> cheers,
>>>
>>> Mollie
>>>
>>>
>>> _______________________________________________
>>> Developers mailing list
>>> Developers at admb-project.org
>>> http://lists.admb-project.org/mailman/listinfo/developers
>>
>> _______________________________________________
>> Developers mailing list
>> Developers at admb-project.org
>> http://lists.admb-project.org/mailman/listinfo/developers
> --
> John Sibert
> Emeritus Researcher, SOEST
> University of Hawaii at Manoa
>
> Visit the ADMB project http://admb-project.org/
>
>
> _______________________________________________
> Developers mailing list
> Developers at admb-project.org
> http://lists.admb-project.org/mailman/listinfo/developers
> _______________________________________________
> Developers mailing list
> Developers at admb-project.org
> http://lists.admb-project.org/mailman/listinfo/developers