On Mon, Feb 15, 2010 at 9:36 AM, CeDeROM <tomek.ce...@gmail.com> wrote:
> Ah yes, OpenOCD's configure script can also assume using
> "/usr/local/lib" and "/usr/local/include" to search for libraries and
> header files - it would be nice, however if it don't the Port will
> make it automatically :-)

Actually I consider this a bug of OpenOCD. /usr/local should
be searched, even under Linux.

> There is also another reason for this to be marked "${LOCALBASE}/lib"
> and "${LOCALBASE}/include" - because one user can set ${LOCALBASE}
> freely to a location different than "/usr/local" (ie.
> /mnt/nfs/server3/usr/local/) and then the Port will have to add/modify
> this location respectively, while the configure script in the
> mainstream would fail to build again as it does not know anything
> about ${LOCALBASE} and in fact there is no need to know :-)

I think under Linux, there is often a pc file (say, libusb-1.0.pc) where
the pkg-config will know the file locations. libusb-0.1 has a program
called libusb-config where you can figure out the location of the
installation.

> You are most welcome and thank you for testing on FreeBSD! You see -
> it was even not a half of a day to get a brand new working and
> functional operating system hahaha! ;P :-)

But I used FreeBSD for a while last time. It is still not fully functional
though since pk2cmd for PICkit 2 is not working yet and there
are some other minor problems. I will debug the problem and
hopefully Hans and others in the FreeBSD USB team can help
me out again.


-- 
Xiaofan http://mcuee.blogspot.com
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to