Follow-up Comment #5, bug #25415 (project gnustep): Hello Peter, Hi Matt,
I'm currently at a trade fair so please excuse my late replies. As you suggested, the reason we cannot automagically link against all GDL2 frameworks is that for gsweb for example, we would start linking in EOInterface and -gui/AppKit which is something we definitely don't want. I had originally considered installing something like separate gdl2-control.make, gdl2-access.make and gdl2-interface.make files, but all these files would contain solely the one line and an include of the dependent library. I figured thatadding the ADDITIONAL_NATIVE_LIBRARY was not really worth the extra files. But maybe it is from a usability standpoint. So what would people think of the approach that we install 4 -make fragments: gdl2.make - merely sets version variables gdl2-control.make - contains ADDITIONAL_NATIVE_LIBRARY += EOControl gdl2-access.make - includes gdl2-control.make and contains ADDITIONAL_NATIVE_LIBRARY += EOControl gdl2-interface.make - includes gdl2-access.make and contains ADDITIONAL_NATIVE_LIBRARY += EOInterface And then you application would simple include gdl2-interface.make It seems a bit overkill to me, but maybe it would make it easier to handle? I do like to get it that issue stabilized though. Cheers, David _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?25415> _______________________________________________ Nachricht geschickt von/durch Savannah http://savannah.gnu.org/ _______________________________________________ Bug-gnustep mailing list Bug-gnustep@gnu.org http://lists.gnu.org/mailman/listinfo/bug-gnustep