Let compilation start in one directory below current one

Let compilation start in one directory below current one

[stephan.zimmer]

I would like to start my compilation in one directory deeper than the
current. Unfortunately, a local variable specification as

% -*- ... compile-directory: (concat default-directory ".."); ... -*-

is not working. Does anyone has an idea (except adding "cd.." to the
compile command)?

Stephan

Re: Let compilation start in one directory below current one

[Rupert Swarbrick]

[-- Attachment #1.1: Type: text/plain, Size: 820 bytes --]

"stephan.zimmer" <stephan.zimmer@googlemail.com> writes:

> I would like to start my compilation in one directory deeper than the
> current. Unfortunately, a local variable specification as
>
> % -*- ... compile-directory: (concat default-directory ".."); ... -*-
>
> is not working. Does anyone has an idea (except adding "cd.." to the
> compile command)?
>
> Stephan

You might be interested in the following code. I wrote it some time ago,
so try not to cringe too much at the horrendous style, but I've been
using it since.

Basically, it looks upwards from where you start to try and find a
configure.ac, which signals the top of an autoconf/automake project. The
selection of filenames to stop at is in the top function. Do what you
will with the code - it's in the public domain as far as I'm concerned.

Rupert


[-- Attachment #1.2: compilepkg.el --]
[-- Type: application/emacs-lisp, Size: 3419 bytes --]

[-- Attachment #2: Type: application/pgp-signature, Size: 314 bytes --]

Re: Let compilation start in one directory below current one

[Kevin Rodgers]

stephan.zimmer wrote:
> I would like to start my compilation in one directory deeper than the
> current. Unfortunately, a local variable specification as
> 
> % -*- ... compile-directory: (concat default-directory ".."); ... -*-
> 
> is not working. Does anyone has an idea (except adding "cd.." to the
> compile command)?

There is no such variable defined or referenced in compile.el.

As far as I know, setting compile-command to "cd .." first is the right
way to do it.

-- 
Kevin Rodgers
Denver, Colorado, USA

Re: Let compilation start in one directory below current one

[Andreas Politz]

Kevin Rodgers wrote:
> stephan.zimmer wrote:
>> I would like to start my compilation in one directory deeper than the
>> current. Unfortunately, a local variable specification as
>>
>> % -*- ... compile-directory: (concat default-directory ".."); ... -*-
>>
>> is not working. Does anyone has an idea (except adding "cd.." to the
>> compile command)?
> 
> There is no such variable defined or referenced in compile.el.
> 
> As far as I know, setting compile-command to "cd .." first is the right
> way to do it.
> 

defun my-compilation-process-setup-function
  ...
  if boundp compile-directory
    setq compile-command ( concat "cd " compile-directory "; " ....


?

-ap

Ps: Due to the economic crisis I am out of parentheses.

Re: Let compilation start in one directory below current one

[stephan.zimmer]

> There is no such variable defined or referenced in compile.el.

Sorry, I meant "compilation-directory". Hopefully, this hasn't created
too much confusion.

> As far as I know, setting compile-command to "cd .." first is the right
> way to do it.

That basically does the job, but then I cannot use the links in the
compilation output to open the files by clicking on them. My hope was
that this is enabled if 'compilation-directory is set correctly.
Furthermore, the "cd.." construction is not really handy.

Maybe, let me generalize my question a bit: Is there any way to use an
elisp function in a local variable specification?

Re: Let compilation start in one directory below current one

[Kevin Rodgers]

stephan.zimmer wrote:
>> There is no such variable defined or referenced in compile.el.
> 
> Sorry, I meant "compilation-directory". Hopefully, this hasn't created
> too much confusion.
> 
>> As far as I know, setting compile-command to "cd .." first is the right
>> way to do it.
> 
> That basically does the job, but then I cannot use the links in the
> compilation output to open the files by clicking on them. My hope was
> that this is enabled if 'compilation-directory is set correctly.
> Furthermore, the "cd.." construction is not really handy.
> 
> Maybe, let me generalize my question a bit: Is there any way to use an
> elisp function in a local variable specification?

Use the eval pseudo-variable.

-- 
Kevin Rodgers
Denver, Colorado, USA

Re: Let compilation start in one directory below current one

[Dan Espen]

"stephan.zimmer" <stephan.zimmer@googlemail.com> writes:

> I would like to start my compilation in one directory deeper than the
> current. Unfortunately, a local variable specification as
>
> % -*- ... compile-directory: (concat default-directory ".."); ... -*-
>
> is not working. Does anyone has an idea (except adding "cd.." to the
> compile command)?

1. compile-command:  cd subdir && make

2. Put cd in the Makefile in the current directory.

3. In make file in current directory, invoke make in the subdirectory

You're requirements may differ, but the 3rd approach is more
"standard".