Started last night `./gradlew bundle` still going...
# kotlin-native
b
Started last night
./gradlew bundle
still going this morning
and done!
s
what kind of computer do you have? That took a long time
b
message has been deleted
I wasn't sure if that was expected or not! maybe I closed the screen before going to sleep and just resumed the build this morning
Now to figure out how to link my multiplatform project against my fork of the project. I've never looked at how grade plugins are built before
k
I’m guessing your machine took a nap.
👍 2
😆 1
s
That’s the exact same machine that I have. It’s much faster for me. I’m guessing Kevin is right.
👍 1
It takes me ~2 hours-ish
k
I get that when I build kotlin native itself. It takes a couple hours, so I’ll leave it on and go do something else. If you forget power saving. it can take much longer than expected
b
Which of these settings do I need to tweak to prevent my machine from napping?
k
If those are default I’d remove the disk drive one, then set the display longer even though that shouldn’t stop anything.
👍 1
s
yeah when i’m doing long-computational processing, I set my display to never turn off. You just have to remember to turn it back after your done, otherwise you’ll kill your display
b
so when the display goes off the mac starts to nap?
maybe better question for macadmins slack, posting there. I'd like to think there is a way I can do long builds without leaving the display on.
k
I’m definitely not an expert. You’d think it would be fine, but my computer sleeps on long builds
b
macadmin folks suggest running
man caffeinate
in terminl
k I will use
caffeinate -i -t 14400
in the future that way I don't have to worry about burning my display. There's a caffeinate option to specify keeping the system from idling until a particular process finishes, but I am not sure of a quick way to get the gradle pid
d
I always used caffeine for my macbook years ago. You can just set the display brightness to zero...
👍 1