<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Craig, welcome :)<br>
<br>
I've added your updates to the developer doc.<br>
<br>
Regards,<br>
Michael<br>
<br>
<div class="moz-cite-prefix">Am 23.06.2018 um 21:49 schrieb Craig
Leres:<br>
</div>
<blockquote type="cite"
cite="mid:5b39f13c-4020-217b-cdb3-689eb3cba39d@xse.com">Initially
I got a build environment up on a spare ubuntu system. But I
wanted to work under FreeBSD so I wrote FreeBSD port for the tool
chain:
<br>
<br>
<a class="moz-txt-link-freetext" href="https://www.freshports.org/devel/xtensa-esp32-elf/">https://www.freshports.org/devel/xtensa-esp32-elf/</a>
<br>
<br>
My ubuntu system says:
<br>
<br>
sea 1 % xtensa-esp32-elf-gcc --version
<br>
xtensa-esp32-elf-gcc (crosstool-NG
crosstool-ng-1.22.0-80-g6c4433a) 5.2.0
<br>
<br>
And FreeBSD says:
<br>
<br>
ice 250 % xtensa-esp32-elf-gcc --version
<br>
xtensa-esp32-elf-gcc (crosstool-NG
crosstool-ng-1.22.0-80-g6c4433a5) 5.2.0
<br>
<br>
So I believe I have the same version. To make the tool chain
available I used:
<br>
<br>
mkdir ~/esp
<br>
ln -s ../../../../../usr/local/xtensa-esp32-elf ~/esp
<br>
<br>
A bonus of having the toolchain under FreeBSD is that (with a
little work) it should be possible to build esp32 arduino sketches
(which BTW is where all of my previous esp8266 and esp32
experience is).
<br>
<br>
In the process of getting this up I ran into a few rough edges.
<br>
<br>
First, on FreeBSD libintl.a is part of the gettext-runtime and
installs with /usr/local as the PREFIX. Attached is the change I
made to esp-idf/tools/kconfig/Makefile. It makes more sense to me
to use -I and -L based on what files are found rather than keying
off OS/OSNAME but I can't easily test this change on Windows. If
this looks ok I can generate a pull request.
<br>
<br>
I had trouble getting a working copy esp-idf. The developer guide
says to check out remotes/origin/release/v2.1 but that version was
giving C errors. Eventually I diff'ed against the copy I had on
ubuntu and found this to be a good set of instructions:
<br>
<br>
git clone <a class="moz-txt-link-freetext" href="https://github.com/openvehicles/esp-idf.git">https://github.com/openvehicles/esp-idf.git</a>
<br>
cd esp-idf
<br>
git submodule update --init
<br>
<br>
I assume the v2.1 step is obsolete. When I need to update it I
use:
<br>
<br>
git pull
<br>
git submodule update
<br>
<br>
(If correct) I think this would worth adding to the developers
guide. (I have to admit I'm pretty inexperienced with git; a
majority of the work I do is with subversion.)
<br>
<br>
The developers guid says to:
<br>
<br>
cp sdkconfig.default sdkconfig
<br>
<br>
This should be updated to
<br>
<br>
cp support/sdkconfig.default.hw31 sdkconfig
<br>
<br>
And there are a lot of new options missing from
support/sdkconfig.default.hw31. Maybe the guide should say, "using
the defaults is usually safe." (Would it be possible to
automatically generate a version of sdkconfig using the defaults
and not asking any questions?)
<br>
<br>
I cloned Open-Vehicle-Monitoring-System-3 and to update it I've
been using:
<br>
<br>
git fetch upstream
<br>
git checkout master
<br>
git merge upstream/master
<br>
git push
<br>
<br>
My module is currently running:
<br>
<br>
3.1.007-2-gc3e62cc-dirty/ota_0/main (build idf
v3.1-dev-987-g55d915e9-dirty Jun 23 2018 12:04:27)
<br>
<br>
built on a FreeBSD 11.1-RELEASE system.
<br>
<br>
Craig
<br>
<br>
P.S. Thanks to Steve for all the offline help.
<br>
<!--'"--><br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.openvehicles.com">OvmsDev@lists.openvehicles.com</a>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="160">--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
</pre>
</body>
</html>