<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
If you want to do builds of local changes without syncing them
between the clones, you can use the same clone by switching the
sdkconfig.<br>
<br>
<tt>vehicle/OVMS.V3> cp sdkconfig tmp/sdkconfig.31</tt><tt><br>
</tt><tt>
vehicle/OVMS.V3> cp tmp/sdkconfig.30 tmp/sdkconfig</tt><tt><br>
</tt><tt>
</tt><br>
Regards,<br>
Michael<br>
<br>
<br>
<div class="moz-cite-prefix">Am 27.01.19 um 09:30 schrieb Stephen
Casner:<br>
</div>
<blockquote type="cite"
cite="mid:alpine.OSX.2.21.9999.1901270029070.67092@auge.attlocal.net">
<pre class="moz-quote-pre" wrap="">What I have done is to clone two separate copies of OVMS code. Only
one copy of esp-idf is needed; both refer to it.
-- Steve
On Sat, 26 Jan 2019, Geir Øyvind Vælidalo wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Hi guys!
I just got hold of a Hyundai Kona and I’ll have it for a few days only. I’ve created a vehicle for Kona / e-Niro and I need to use the developer card with the version 3.0 hardware as the 3.1 is used in my Soul. Switching between both HW3.1 and HW3.0 seems cumbersome. Are there any easy ways to switch between them when building? We’ll get out new e-Niro in a few weeks, so it would be nice to build for both hardware versions without to much hassle.
Best regards,
Geir</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-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>
</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>