Building Emacs on two different OSes from a shared directory

Building Emacs on two different OSes from a shared directory

[Dani Moncayo]

Hello,

I have Ubuntu installed on one machine, and Windows 7 installed on top
of it as a virtual machine (made with VirtualBox).

If I have a mirror of Emacs trunk in Ubuntu, and that directory tree
is also accessible from Windows (it's a shared folder), can I build
Emacs correctly on both OSes from that same repository, or could there
be some problem?

TIA.

-- 
Dani Moncayo

Re: Building Emacs on two different OSes from a shared directory

[Xue Fuqiao]

On Mon, 28 Jan 2013 08:48:03 +0100
Dani Moncayo <dmoncayo@gmail.com> wrote:

> I have Ubuntu installed on one machine, and Windows 7 installed on top
> of it as a virtual machine (made with VirtualBox).
> 
> If I have a mirror of Emacs trunk in Ubuntu, and that directory tree
> is also accessible from Windows (it's a shared folder), can I build
> Emacs correctly on both OSes from that same repository, or could there
> be some problem?

I think you can.  Just use two seperate branches in one repository:

      cd emacs
      bzr branch trunk/ BRANCHNAME/

-- 
Best regards, Xue Fuqiao.
http://www.emacswiki.org/emacs/XueFuqiao

Re: Building Emacs on two different OSes from a shared directory

[Dani Moncayo]

>> I have Ubuntu installed on one machine, and Windows 7 installed on top
>> of it as a virtual machine (made with VirtualBox).
>>
>> If I have a mirror of Emacs trunk in Ubuntu, and that directory tree
>> is also accessible from Windows (it's a shared folder), can I build
>> Emacs correctly on both OSes from that same repository, or could there
>> be some problem?
>
> I think you can.  Just use two seperate branches in one repository:
>
>       cd emacs
>       bzr branch trunk/ BRANCHNAME/

Of course, if I make a separate branch for each OS, there should not
be any problem, but the question is whether I could compile Emacs on
both OSes using the same directory tree.

AFAIK, the build on MS-Windows is done entirely under the "nt/"
subdirectory which is specific to that platform.  If that is true,
there should be no problem is sharing the same directory tree for both
OSes.


-- 
Dani Moncayo

Re: Building Emacs on two different OSes from a shared directory

[Xue Fuqiao]

On Mon, 28 Jan 2013 10:38:55 +0100
Dani Moncayo <dmoncayo@gmail.com> wrote:

> Of course, if I make a separate branch for each OS, there should not
> be any problem, but the question is whether I could compile Emacs on
> both OSes using the same directory tree.

The GNU Build System distinguishes two trees: the source tree, and the build tree.  So I think you can do it.

> AFAIK, the build on MS-Windows is done entirely under the "nt/"
> subdirectory which is specific to that platform.  If that is true,
> there should be no problem is sharing the same directory tree for both
> OSes.

I have never built Emacs on w32, so I have no idea.

-- 
Best regards, Xue Fuqiao.
http://www.emacswiki.org/emacs/XueFuqiao

Re: Building Emacs on two different OSes from a shared directory

[Harald Hanche-Olsen]

[Xue Fuqiao <xfq.free@gmail.com> (2013-01-28 09:53:46 UTC)]

> On Mon, 28 Jan 2013 10:38:55 +0100
> Dani Moncayo <dmoncayo@gmail.com> wrote:
> 
> > Of course, if I make a separate branch for each OS, there should not
> > be any problem, but the question is whether I could compile Emacs on
> > both OSes using the same directory tree.
> 
> The GNU Build System distinguishes two trees: the source tree, and the build tree.  So I think you can do it.

One way to do that would be, on architecture foo:

./autogen.sh
mkdir build_foo
cd build_foo
../configure
make

I am not too sure if autogen.sh has results that are incompatible between architectures, though, so you might not get away with building for architectures foo and bar at the same time.

- Harald

Re: Building Emacs on two different OSes from a shared directory

[Eli Zaretskii]

> Date: Mon, 28 Jan 2013 10:38:55 +0100
> From: Dani Moncayo <dmoncayo@gmail.com>
> Cc: Emacs development discussions <emacs-devel@gnu.org>
> 
> AFAIK, the build on MS-Windows is done entirely under the "nt/"
> subdirectory which is specific to that platform.

The Windows build is _started_ in the nt/ directory.  But then the
Makefiles recurse into the other directories: src, lib, lib-src, etc.,
and build files there as well.

It is however, true that compiled files are placed in subdirectories,
like nt/oo/i386, src/oo/i386, etc. -- different set of directories for
each architecture and optimization level.  So compiling on Unix will
not overwrite Windows object files and executables.

Re: Building Emacs on two different OSes from a shared directory

[Dani Moncayo]

>> AFAIK, the build on MS-Windows is done entirely under the "nt/"
>> subdirectory which is specific to that platform.
>
> The Windows build is _started_ in the nt/ directory.  But then the
> Makefiles recurse into the other directories: src, lib, lib-src, etc.,
> and build files there as well.
>
> It is however, true that compiled files are placed in subdirectories,
> like nt/oo/i386, src/oo/i386, etc. -- different set of directories for
> each architecture and optimization level.  So compiling on Unix will
> not overwrite Windows object files and executables.

Understood, thanks.  I presume this is true also for "make install".

-- 
Dani Moncayo

Re: Building Emacs on two different OSes from a shared directory

[Eli Zaretskii]

> Date: Mon, 28 Jan 2013 15:29:35 +0100
> From: Dani Moncayo <dmoncayo@gmail.com>
> Cc: xfq.free@gmail.com, emacs-devel@gnu.org
> 
> >> AFAIK, the build on MS-Windows is done entirely under the "nt/"
> >> subdirectory which is specific to that platform.
> >
> > The Windows build is _started_ in the nt/ directory.  But then the
> > Makefiles recurse into the other directories: src, lib, lib-src, etc.,
> > and build files there as well.
> >
> > It is however, true that compiled files are placed in subdirectories,
> > like nt/oo/i386, src/oo/i386, etc. -- different set of directories for
> > each architecture and optimization level.  So compiling on Unix will
> > not overwrite Windows object files and executables.
> 
> Understood, thanks.  I presume this is true also for "make install".

Yes, see install-other-dirs-gmake.

Re: Building Emacs on two different OSes from a shared directory

[Andreas Schwab]

Xue Fuqiao <xfq.free@gmail.com> writes:

> I think you can.  Just use two seperate branches in one repository:

You don't need to copy the sources, just use separate build directories.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: Building Emacs on two different OSes from a shared directory

[Eli Zaretskii]

> Date: Mon, 28 Jan 2013 08:48:03 +0100
> From: Dani Moncayo <dmoncayo@gmail.com>
> 
> I have Ubuntu installed on one machine, and Windows 7 installed on top
> of it as a virtual machine (made with VirtualBox).
> 
> If I have a mirror of Emacs trunk in Ubuntu, and that directory tree
> is also accessible from Windows (it's a shared folder), can I build
> Emacs correctly on both OSes from that same repository, or could there
> be some problem?

You can build in the same tree, if you want: since the Windows build
places the compiled files in subdirectories (src/oo/i386 etc.), and
the Unix build places them in the same directory as sources, there
should be no conflict.

On Unix, you can also build outside of the source tree:

  mkdir /some/where/else
  cd /some/where/else
  /path/to/emacs/tree/configure ...
  make

In the latter case, the source directories will remain clean.

Re: Building Emacs on two different OSes from a shared directory

[Dani Moncayo]

> You can build in the same tree, if you want: since the Windows build
> places the compiled files in subdirectories (src/oo/i386 etc.), and
> the Unix build places them in the same directory as sources, there
> should be no conflict.
>
> On Unix, you can also build outside of the source tree:
>
>   mkdir /some/where/else
>   cd /some/where/else
>   /path/to/emacs/tree/configure ...
>   make
>
> In the latter case, the source directories will remain clean.

Great.  Thank you.

-- 
Dani Moncayo