configure.in

[Ian D. Stewart]

Howdy Folks,

I'm walking through 'IMPLEMENTING A NEW DLL' in DEVELOPER-HINTS.  Step 
3 reads:

Add the directory (and the generated .o file for the module) in:     + 
./configure.in (in AC_OUTPUT macro at the end of the file to
       trigger the Makefile generation),
     + ./Makefile.in (in LIBSUBDIRS and LIBOBJS macros)
     + ./dlls/Makefile.in (in SUBDIRS macro)

Far as I can tell, there is no configure.in.  The closest I could find 
is configure.ac.  Is this the file that needs to be edited, or am I 
missing something?

Thanx,
Ian

[Francois Gouget]

On Mon, 13 May 2002, Ian D. Stewart wrote:
> Howdy Folks,
>
> I'm walking through 'IMPLEMENTING A NEW DLL' in DEVELOPER-HINTS.  Step
> 3 reads:
>
> Add the directory (and the generated .o file for the module) in:     +
> ./configure.in (in AC_OUTPUT macro at the end of the file to
>        trigger the Makefile generation),
>      + ./Makefile.in (in LIBSUBDIRS and LIBOBJS macros)
>      + ./dlls/Makefile.in (in SUBDIRS macro)
>
> Far as I can tell, there is no configure.in.  The closest I could find
> is configure.ac.  Is this the file that needs to be edited, or am I
> missing something?

I did not see any reply so I will reply. configure.in was renamed to
configure.ac when Wine switched to AutoConf 2.5x. I guess the AutoConf
project switched to .ac to distinguish this file from the other .in
files.

--
Francois Gouget         [e-mail]        http://fgouget.free.fr/
     Linux, WinNT, MS-DOS - also known as the Good, the Bad and the Ugly.

[Alexandre Julliard]

"Ian D. Stewart"  writes:
> I'm walking through 'IMPLEMENTING A NEW DLL' in DEVELOPER-HINTS.  Step
> 3 reads:

Actually this whole 'implementing a new dll' section is completely
obsolete (like most of the rest of the file), it needs to be rewritten
from scratch, and probably belongs in the Wine developer's guide
instead.

[Ian D. Stewart]

On 2002.05.14 16:06 Alexandre Julliard wrote:
> "Ian D. Stewart"  writes:
> > I'm walking through 'IMPLEMENTING A NEW DLL' in DEVELOPER-HINTS.
>
> Step
> > 3 reads:
>
> Actually this whole 'implementing a new dll' section is completely
> obsolete (like most of the rest of the file), it needs to be rewritten
> from scratch, and probably belongs in the Wine developer's guide
> instead.

Is there enough information to implement a new DLL (i.e., is it just 
the file references that are out of date), or should I wait for the 
rewrite?

Thanx,
Ian

[Alexandre Julliard]

"Ian D. Stewart"  writes:
> Is there enough information to implement a new DLL (i.e., is it just
> the file references that are out of date), or should I wait for the
> rewrite?

Adding a dll should be easier now, so you can simply ignore all
instructions that don't seem to apply. Basically the steps would be
something like:

- create directory under dlls/  (16 and 32-bit versions of the dll
  need to be in the same directory)
- create Makefile.in and .spec file in that directory
- add Makefile.in in configure.ac AC_CONFIG_FILES list
- run make_dlls in dlls/ directory
- run configure and make