Re: [feature/native-comp] breakage on build

[Óscar Fuentes]

Óscar Fuentes <ofv@wanadoo.es> writes:

> Phillip Lord <phillip.lord@russet.org.uk> writes:
>
>> So, I did this:
>>
>>  - Installed a fresh msys to a clean directory on my desktop.
>>  - Dropped the emacs-no-deps.zip directory on top of the mingw64 directory.
>>  - clicked on runemacs.exe from windows shell -- Emacs fails to launch
>>    because of libgmp
>>  - pacman installed all the dependencies of Emacs
>>  - clicked on runemacs.exe -- Emacs launches, native-comp fails as
>>    described
>>  - run mingw64 shell form the mys installation
>>  - ./runemacs.exe in that shell
>>  - Emacs launches, native-comp works
>>  - ~/ and thus ~/.emacs.d/eln-cache is a different location with the two
>>    launch methods
>>
>> I believe that msys is mostly portable and a new installation is nearly
>> clean (except for .bashrc and such like).
>>
>> Conclusions:
>>
>>  - emacs is picking up dependencies from mingw64 run in either way,
>>    because otherwise it wouldn't run at all from the shell
>>  - Emacs is picking up the environment from mingw64 when launched from
>>    within it, hence the differences in location of ~
>>  - Native-comp has everything it needs to run, or it couldn't run at
>>    all.
>>  - It is missing something from the environment when run in the windows
>>    shell.
>>
>> This is export run inside the mingw64 window. So, lots of options there.
>
> If, at the top of .emacs.el, you add the binary directory of emacs.exe
> to exec-path, does native-comp work when you start emacs from the
> desktop's icon?
>
> Also, some days ago I sent you an e-mail off-list. Have you seen it?

On second thought, exec-path solves the problem of emacs.exe running
other executables, but it is not enough when those executables run other
executables on turn. So emacs.exe will launch gcc.exe just fine, but
gcc.exe will fail to run as.exe, ld.exe, etc.

So we must set PATH too.