Mailing-List: contact modules-dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: modules-dev@httpd.apache.org
Received-SPF: pass (athena.apache.org: domain of jmarantz@google.com
 designates 209.85.217.173 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4FD67F10.2080702@smartechhomes.com>
References: 
 <CADc7B-LXjBB3VWLnKEPvpJDKchq9HBLVJsOHJU7S+hB94k0+fQ@mail.gmail.com>
	<CAHQurc-ttHOGL_npAVYvMNtmGiDuwv0U55jj7+oEg-28T1bAdQ@mail.gmail.com>
	<4FD67F10.2080702@smartechhomes.com>
Date: Mon, 11 Jun 2012 19:40:41 -0400
Message-ID: 
 <CAGKR+EBf+WQMcO=9CKLgByoihuMGu=Jy9nK7yTDgU9sbz5vu9A@mail.gmail.com>
Subject: Re: Get the directory of the module
From: Joshua Marantz <jmarantz@google.com>
To: modules-dev@httpd.apache.org
Content-Type: multipart/alternative; boundary=f46d0435c1d2c17be004c23ae052

--f46d0435c1d2c17be004c23ae052
Content-Type: text/plain; charset=ISO-8859-1

I think he wants to write bytecodes during module installation when he will
have write access.

During installation can you also write a .conf template showing your module
where the bytecodes are?

Josh
 On Jun 11, 2012 7:29 PM, "Jerry Stuckle" <jerry@smartechhomes.com> wrote:

>
>
> On 6/11/2012 5:49 PM, Ben Noordhuis wrote:
>
>> On Mon, Jun 11, 2012 at 10:10 PM, Bart Wiegmans<bartwiegmans@gmail.**com<bartwiegmans@gmail.com>>
>>  wrote:
>>
>>> Hello everybody,
>>>
>>> For a project I'm doing, I need to install a few bytecode files
>>> alongside my module. I was planning on placing them in the modules
>>> directory but I realised that at runtime I do not know where that is.
>>> What is more, that directory may (and will, as a matter of fact) vary
>>> during installation and testing. But most importantly, the server
>>> knows where the module is kept as it specified by LoadModule.
>>>
>>> So in short, how can I determine the directory of my module at runtime?
>>>
>>
>> You can't, the file path is internal to mod_so.c. I don't think it
>> even stores it.
>>
>>
>>
> In addition, there is no guarantee you have write access to that directory.
>

--f46d0435c1d2c17be004c23ae052--