j2objc Build #2064
Comments
|
Well, thanks DEEP-Dh for the reply from ChatGPT 1.0 Alpha. |
|
The build should work with a fix from this morning: either sync your repo
clone or patch in
fd32981
.
(Not ChatGPT or Bard here :-)
…On Mon, Apr 24, 2023 at 11:50 AM Kelv ***@***.***> wrote:
Well, thanks DEEP-Dh for the reply from ChatGPT 1.0 Alpha.
—
Reply to this email directly, view it on GitHub
<#2064 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAW2JLZMIWMJ3IS3FNLNV73XC24M5ANCNFSM6AAAAAAXFPWE3A>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
|
Thank you very much. Much better than AI :) One more thing. Is there a specific version of protobuf needed? I tried
|
|
Argh, a protobuf engineer did a header cleanup recently and broke our
protobuf build. Sorry about that.
Until this gets fixed, you can run "brew install protobuf", then set
PROTOBUF_ROOT_DIR to /usr/local (or wherever your Homebrew home is). To
verify the variable is correct, run "$PROTOBUF_ROOT_DIR/bin/protoc
--version", which should return "libprotoc 3.21.12".
…On Mon, Apr 24, 2023 at 2:33 PM Kelv ***@***.***> wrote:
Thank you very much. Much better than AI :)
One more thing. Is there a specific version of protobuf needed? I tried libprotoc
3.3.0 (brew install protobuf delivers this) and a fresh build of the
latest version of libprotoc 22.3, both have the same problem:
fatal error: 'google/protobuf/stubs/strutil.h' file not found
—
Reply to this email directly, view it on GitHub
<#2064 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAW2JL5OUW3DODT4FBG7IULXC3PTJANCNFSM6AAAAAAXFPWE3A>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
Successfully built. One more thing (there's always one more :). Are there any special settings needed for bitcode activation?
Your build (2.3) does not have this problem. |
|
You can roll back
3431295,
which removed bitcode since Xcode 14 deprecates it. We jumped on that
because we've been blocked on new releases because of GitHub max binary
limits, and this will reduce our release bundle size.
…On Tue, Apr 25, 2023 at 9:44 AM Kelv ***@***.***> wrote:
Successfully built. One more thing (there's always one more :). Are there
any special settings needed for bitcode activation?
Xcode 14.2 on Monterey reports:
'.../j2objc/lib/iphone/libjre_emul.a(ErrnoException.o)' does not contain
bitcode. You must rebuild it with bitcode enabled (Xcode setting
ENABLE_BITCODE), obtain an updated library from the vendor, or disable
bitcode for this target. file '.../j2objc/lib/iphone/libjre_emul.a' for
architecture arm64
Your build (2.3) does not have this problem.
—
Reply to this email directly, view it on GitHub
<#2064 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAW2JL7RI6DH5P4ER22QP2LXC7WN7ANCNFSM6AAAAAAXFPWE3A>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
Xcode 14 deprecates bitcode - but why?
<https://stackoverflow.com/questions/72543728/xcode-14-deprecates-bitcode-but-why>
…On Tue, Apr 25, 2023 at 10:10 AM Tom Ball ***@***.***> wrote:
You can roll back
3431295,
which removed bitcode since Xcode 14 deprecates it. We jumped on that
because we've been blocked on new releases because of GitHub max binary
limits, and this will reduce our release bundle size.
On Tue, Apr 25, 2023 at 9:44 AM Kelv ***@***.***> wrote:
> Successfully built. One more thing (there's always one more :). Are there
> any special settings needed for bitcode activation?
> Xcode 14.2 on Monterey reports:
>
> '.../j2objc/lib/iphone/libjre_emul.a(ErrnoException.o)' does not contain
> bitcode. You must rebuild it with bitcode enabled (Xcode setting
> ENABLE_BITCODE), obtain an updated library from the vendor, or disable
> bitcode for this target. file '.../j2objc/lib/iphone/libjre_emul.a' for
> architecture arm64
>
> Your build (2.3) does not have this problem.
>
> —
> Reply to this email directly, view it on GitHub
> <#2064 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAW2JL7RI6DH5P4ER22QP2LXC7WN7ANCNFSM6AAAAAAXFPWE3A>
> .
> You are receiving this because you commented.Message ID:
> ***@***.***>
>
|
|
Thanks for the clarification, I didn't notice the deprecation at all. |
|
I like that StackOverflow answer, as it explains why much better than Apple
did.
…On Tue, Apr 25, 2023 at 10:20 AM Kelv ***@***.***> wrote:
Thanks for the clarification, I didn't notice the deprecation at all.
—
Reply to this email directly, view it on GitHub
<#2064 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAW2JLYPISXGMNW2YADJ3YTXC72U3ANCNFSM6AAAAAAXFPWE3A>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Have you tried the full j2objc build lately?
I am trying to follow the instructions:
https://developers.google.com/j2objc/guides/building-j2objc
But the last buildable commits are half a year old.
The latest version throws a lot of
not supported in -source 8 errorsright at the start. At the same time,java.mkexplicitly states-source 1.8 -target 1.8. If I change it, more errors are thrown, and so on and on.The text was updated successfully, but these errors were encountered: