Base Pr1me writes: > Yes, I am installing the crosstool-NG to the working directory to create the > final, actual needed product. I wondered if this was violating some ports > methodology. > > Before I did that, crosstool-NG was just installing itself to the > system. EEK! It was an ugly mess. > > I'll have to see what can be done with a two-ports approach. > However, after the xtensa install, I wouldn't want the crosstool just > hanging > around on my system, hence the reason for putting it in the pobj directory > to > build from there and be cleaned up. All it is good for is generating > xtensa-lx106-elf.
The way to do that in ports is to use it as a BUILD_DEPENDS. Then the crosstools-ng package only needs to be installed in order to build the compiler, and can be uninstalled afterward. > The lx106 branch has been changed to specifically build the compilers needed > for esp8266 chips and their hardware abstraction layer elements. The master > crosstool-NG branch will not build this. Why not? Is there a way to contribute those modifications upstream? -- Anthony J. Bentley
