[Opensim-dev] Package manager

[Mic Bowman]

even non-dll's need to be in bin. that was the problem. you can't both copy
the ini file into bin/dispatcher on build through prebuild:

<Match pattern="*.ini.example" buildAction="Copy"
destination="../../bin/dispatcher" />

 and have the assembly install them into a subdirectory like this:

[assembly: ImportAddinFile("dispatcher/Dispatcher.ini.example")]

mautil tries to find dispatcher/dispatcher/Dispatcher.ini.example

you get one or the other.



On Tue, Jan 6, 2015 at 12:32 PM, Diva Canto <diva at metaverseink.com> wrote:

>  On 1/6/2015 10:30 AM, Mic Bowman wrote:
>
> When i explicitly put the build libraries into bin/dispatcher (so that
> would be DispatcherModule.dll), they do not appear to be loaded on OpenSim
> startup. The module init function is never called.
>
>  Just coming back to... we have two situations.. build from source into
> an runnable deployment and install modules into an existing runnable
> deployment. The rules for the two seem to be different for how addins are
> loaded.
>
>
> Yes. If you want to run the code from the same source in which you build,
> you need to have those dlls in bin. I suspected you were doing that, that's
> why I suggested you place the dlls in bin and the other non-dll files in a
> subfolder.
>
> On my side of things, I don't run from the tree in which I build, so I do
> things slightly differently.
>
>
> On Tue Jan 06 2015 at 10:11:25 AM Mic Bowman <cmickeyb at gmail.com> wrote:
>
>> Couple more questions... i have several directories of stuff: documents,
>> scripts, etc. Do I need to list every single file using the
>> ImportAddinFile? Also, I want two separate packages to be created, one for
>> the dispatcher and one for the remote control messages and handlers. that
>> implies two separate prebuild projects?
>>
>> On Tue Jan 06 2015 at 8:40:24 AM Diva Canto <diva at metaverseink.com>
>> wrote:
>>
>>> On 1/6/2015 8:31 AM, Diva Canto wrote:
>>> > In my tests, mono addins does the right thing with dependencies! For
>>> > example, Diva.Wifi (which is now an addin) depends on another addin
>>> > Diva.Interfaces (this one defines an extension point for Wifi -- I
>>> > have extra packages that aren't in the free distribution of Wifi).
>>> > When you install Diva.Wifi, it correctly installs Diva.Interfaces
>>> > automatically. The interface is very similar to yum or apt-get, it
>>> > lets you know about the dependencies, and asks you if you want to
>>> > proceed.
>>>
>>> Forgot to say this: and if Diva.Interfaces (the common package) is
>>> already installed by the time Diva.Wifi is installed, all the better. In
>>> other words, bugs not withstanding, mono addins is behaving like you
>>> would expect a package manager to behave.
>>>
>>> _______________________________________________
>>> Opensim-dev mailing list
>>> Opensim-dev at opensimulator.org
>>> http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-dev
>>>
>>
>
> _______________________________________________
> Opensim-dev mailing listOpensim-dev at opensimulator.orghttp://opensimulator.org/cgi-bin/mailman/listinfo/opensim-dev
>
>
>
> _______________________________________________
> Opensim-dev mailing list
> Opensim-dev at opensimulator.org
> http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://opensimulator.org/pipermail/opensim-dev/attachments/20150106/5f9f011d/attachment.html>