On Fri, Oct 4, 2019 at 6:47 PM Don Lewis <[email protected]> wrote:
> On 4 Oct, [email protected] wrote: > > > diff --git a/main/codemaker/Executable_cppumaker.mk > b/main/codemaker/Executable_cppumaker.mk > > index b876b68..63c9bc2 100644 > > --- a/main/codemaker/Executable_cppumaker.mk > > +++ b/main/codemaker/Executable_cppumaker.mk > > @@ -25,9 +25,9 @@ $(eval $(call gb_Executable_Executable,cppumaker)) > > > > $(eval $(call gb_Executable_set_targettype_gui,cppumaker,NO)) > > > > -$(eval $(call > gb_StaticLibrary_add_package_headers,cppumaker,codemaker_inc)) > > +$(eval $(call > gb_Executable_add_package_headers,cppumaker,codemaker_inc)) > > Does anyone know why we call add_package_headers when building > executables? When building libraries, we need to deliver the headers > for the library API, but I don't know why we would do this for an > executable. > > If you look at 529d6db8d002a57de885f2a2dfd65c2a89b9309e the old prj/d.lst was delivering headers too, so I just did the same in gbuild. Some other downstream module probably needs them.
