Return-Path: Message-Id: <847649876@web.de> MIME-Version: 1.0 From: "Martin Mueller" To: bluez-devel@lists.sourceforge.net Subject: Re: [Bluez-devel] cross compiling bluez-utils Content-Type: text/plain; charset="iso-8859-1" Sender: bluez-devel-admin@lists.sourceforge.net Errors-To: bluez-devel-admin@lists.sourceforge.net Reply-To: bluez-devel@lists.sourceforge.net List-Unsubscribe: , List-Id: BlueZ development List-Post: List-Help: List-Subscribe: , List-Archive: Date: Fri, 04 Feb 2005 13:44:47 +0100 Hi Marcel, > > does it make sense to change the line "sysconfdir='${prefix}/etc'" into "sysconfdir='${exec_prefix}/etc'" in the configure file? I found that useful while compiling the utils for an ARM platform. The /etc will be generated in the right place then. > > explain what the differences are. However the acinclude.m4 is a little > bit more complex and there are other corner cases. just curious - I have no real idea what I am doing... If I compile it the way it is the /etc/bluetooth/ files will be generated in the cross compiler folders. It looks a little lost there. If I change that to the exec_prefix area, it will be directly put into my ramdisk where the /sbin files and all the rest go. Martin ______________________________________________________________ Verschicken Sie romantische, coole und witzige Bilder per SMS! Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193 ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ Bluez-devel mailing list Bluez-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-devel