> I wonder how many other bumps we will find :-( > > --- Duane. FreeBSD: Well, I'm not really qualified to say, but I'll try. I started this conversation with Rick awhile back and didn't manage to follow up. I just want to "port" OOCD into the 'standard' freebsd port build system. I want no special toys, ftd2xx or whatever. I'd like minimal support for all dongles (the last person to try a port of urjtag just disabled all the dongles because they couldn't figure out how to find libftdi - how useful - I'll try not to repeat that). So, the only hiccup is that we use /usr/local/include for everything instead of /usr/include (or /include?). Anyways, the bare configure can't seem to handle that (although it seems to find all the other includes fine, just not libftdi). So, should I be doing the identical thing with --includedir and --libdir or --with-libftdi= that you are doing with ftd2xx, or should I be mangling the CFLAGS? Seems the other port scripts I've seen do it with configure, but as with all open source, that doesn't make them 'correct', just functional. If I should be just mangling the CFLAGS, why aren't we just mangling the CFLAGS for ftd2xx? I suspect the answer to that question may make it obvious what I should be doing.
Best, Steve _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
