Hi,
when I run git submodule status, I get the following output:
$ git submodule status
7b953e7ebb440ce9461ee469159c3759450e7c98
vehicle/OVMS.V3/components/mongoose/mongoose
(6.2-882-g7b953e7)
c05f6c7530a8670e3d0ffdf04ee4cecb2d3b0496
vehicle/OVMS.V3/components/wolfssh/wolfssh (v1.4.10-stable)
9ffa9faecda87a7c0ce7521c83996c65d4e86943
vehicle/OVMS.V3/components/wolfssl/wolfssl (v5.6.2-stable)
7c3878f8302c0e84578a67473e49e60bc6b3ada7
vehicle/OVMS.V3/components/zip/libzip (rel-1-5-1-60-g7c3878f)
d6bcf4ca4d02479f058fff44cfd171f928148179
vehicle/OVMS.V3/components/zip/zlib (v1.2.11-65-gd6bcf4c)
I had the problem that after a git pull wolfssl was removed from
my local source.
git submodule status then showed:
$ git submodule status
23e018e58f15a238c8c77ebdf724a2b18ad5f28a
vehicle/OVMS.V3/components/mongoose/mongoose (6.2-880-g23e018e)
c05f6c7530a8670e3d0ffdf04ee4cecb2d3b0496
vehicle/OVMS.V3/components/wolfssh/wolfssh (v1.4.10-stable)
6ffb692964ec2dc7fae21790fb5bb13b4ef2ed94
vehicle/OVMS.V3/components/zip/libzip (rel-1-5-1-58-g6ffb692)
d6bcf4ca4d02479f058fff44cfd171f928148179
vehicle/OVMS.V3/components/zip/zlib (v1.2.11-65-gd6bcf4c)
I then ran '
git submodule update --init
--recursive' as described.
But although the module was present in .gitmodules, it was not
downloaded.
I then used
$ git submodule add
https://github.com/openvehicles/wolfssl.git
vehicle/OVMS.V3/components/wolfssl/wolfssl
to add it manually.
But now my code no longer compiles.
I get the following error message during compile
make[1]: *** No rule to make target
'wolfssl/wolfcrypt/src/hc128.o', needed by 'libwolfssl.a'.
Stop.
Is it because I now have version v5.6.2 of wolfssl instead of the
expected submodule version v4.7.0?
How can I get my submobules to be included in the required version
again?
I would be grateful for any help!
Kind regards,
Simon
Am 17.05.2023 um 23:24 schrieb Ludovic LANGE:
Dear all,
The PR
https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/pull/887
which converts wolfssl to a git submodule has been merged to
master.
For those that build / sync their trees manually, please ensure
that you do `git submodule update --init
--recursive` after the git pull, so that you can
properly retrieve the submodule.
You can confirm that everything is OK by doing:
$ git submodule status
7b953e7ebb440ce9461ee469159c3759450e7c98
components/mongoose/mongoose (6.2-882-g7b953e7)
c05f6c7530a8670e3d0ffdf04ee4cecb2d3b0496
components/wolfssh/wolfssh (v1.4.10-stable)
2d5a0ccae50a2ea32fc933d707b465520cc90011
components/wolfssl/wolfssl (v4.7.0-stable-5-g2d5a0ccae)
7c3878f8302c0e84578a67473e49e60bc6b3ada7
components/zip/libzip (rel-1-5-1-60-g7c3878f)
d6bcf4ca4d02479f058fff44cfd171f928148179 components/zip/zlib
(v1.2.11-65-gd6bcf4c)
It should print (3rd line) a version of v4.7.0-stable-5-g2d5a0ccae.
If instead you see:
$ git submodule status
7b953e7ebb440ce9461ee469159c3759450e7c98
components/mongoose/mongoose (6.2-882-g7b953e7)
c05f6c7530a8670e3d0ffdf04ee4cecb2d3b0496
components/wolfssh/wolfssh (v1.4.10-stable)
-2d5a0ccae50a2ea32fc933d707b465520cc90011
components/wolfssl/wolfssl
7c3878f8302c0e84578a67473e49e60bc6b3ada7
components/zip/libzip (rel-1-5-1-60-g7c3878f)
d6bcf4ca4d02479f058fff44cfd171f928148179 components/zip/zlib
(v1.2.11-65-gd6bcf4c)
then you need to use `git submodule
update --init --recursive`
Let me know if it's not working according to the plan.
Regards,
_______________________________________________
OvmsDev mailing list
OvmsDev@lists.openvehicles.com
http://lists.openvehicles.com/mailman/listinfo/ovmsdev