On Mon, Feb 15, 2010 at 1:21 AM, Xiaofan Chen <xiaof...@gmail.com> wrote:
> On Mon, Feb 15, 2010 at 9:13 AM, Xiaofan Chen <xiaof...@gmail.com> wrote:
>>> and there are some addtional libraries/includes passed to the compiler
>>> in the Makefile:
> (...)
>> I think the above patches should be integrated into the main
>> OpenOCD source tree.
>
> Or maybe I should say the other way, the configure script in
> OpenOCD may be improved to have better libftdi support.

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 :-)

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 :-)


>>> Please use the provided port for RC2 (and verify if it works fine for
>>> you), or analyze the Makefile and apply the environment for your need
>>> :-)
>>
>> Thanks, your RC2 port seems to work fine. I have not tried the
>> real thing, but the build process is smooth.
>>
>
> A minor thing, the file name "pkg-plist.rc1" might be better named
> "pkg-plist.rc2".

Well its just my curiosity - the *.rc1 file is a backup from RC1 Port
to see how installed files changed from RC1 to RC2 - it will be
removed in official port :-)

> Thanks a lot for the helps.

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 :-)

Best regards! :-)
Tomek Cedro

-- 
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to