mautil doesn't care where the dlls are. It just assumes that the paths
in the directives are relative to where the packaged dll is.
On 1/6/2015 10:36 AM, Mic Bowman wrote:
And the file path problem persists with the ini files... so I have
included the config file under dispatcher/Dispather.ini.example in the
addins statement. I copy that file on build from source into a
directory called bin/dispatcher and also copy the dll into that
directory (using the prebuild paths). when i run mautil pack i get a
bunch of errors related to the path dispatcher/dispatcher. It appears
that I *must* build into bin when building from source, then create
the package, which will then unpack into the directory structure that
I want.
On Tue Jan 06 2015 at 10:30:45 AM Mic Bowman <[email protected]
<mailto:[email protected]>> 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.
On Tue Jan 06 2015 at 10:11:25 AM Mic Bowman <[email protected]
<mailto:[email protected]>> 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
<[email protected] <mailto:[email protected]>> 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
[email protected]
<mailto:[email protected]>
http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-dev
_______________________________________________
Opensim-dev mailing list
[email protected]
http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-dev
_______________________________________________
Opensim-dev mailing list
[email protected]
http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-dev
