Yes, it work unchanged on 64 bit ARM. I have not cross compiled on AMD for ARM. We added the ability to provide the target triple but don't know how the rest of that process works - install the ARM includes and libs? If you can achieve this is would be great to add a How-to in the docs. All we have so far - https://scala-native.readthedocs.io/en/latest/user/sbt.html#cross-compilation-using-target-triple
Hi folks, I've probably tried something wrong: I wanted to apply Scala Native on a small Vert.x application. I get the error message (on MacOS):
[error] (Compile / nativeLink) java.lang.ClassCastException: class scala.scalanative.linker.Unavailable cannot be cast to class scala.scalanative.linker.ScopeInfo (scala.scalanative.linker.Unavailable and scala.scalanative.linker.ScopeInfo are in unnamed module of loader sbt.internal.PluginManagement$PluginClassLoader @41da3aee)Is this something that should work? My impression so far is that Scala Native is for more basic applications.
There is also a newer chat for Scala Native here - https://discord.gg/scala
We can continue here but most of the group follows over there for Scala.
For matrix users, we now have #scala-native:matrix.org which is (or will shortly be) bridged into the Scala Native Discord channel
ERROR: insufficient permissions to use this command! Try
!discord help to see all available commands
Hello everyone. How do I get access to a #define XXX in Scala ? the @extern , @name and other goodies work as long as it is a function but doesn't find the #defines :
@link("glfw")
@extern
object glfw {
@name("GLFW_CLIENT_API")
def CLIENT_API: CInt = extern
@name("GLFW_NO_API")
def NO_API: CInt = extern
@name("glfwWindowHint")
def windowHint(a: Unit, b: Unit): Unit = extern
}finds the glfwWindowHint but not GLFW_CLIENT_API and GLFW_NO_API
[error] Undefined symbols for architecture x86_64:
[error] "_GLFW_CLIENT_API", referenced from:
[error] __SM5Main$D4mainLAL16java.lang.String_uEO in 2.ll.o
[error] "_GLFW_NO_API", referenced from:
[error] __SM5Main$D4mainLAL16java.lang.String_uEO in 2.ll.o
[error] ld: symbol(s) not found for architecture x86_64
Currently I don't think you can access defs directly.
You can write a forwarder function in C (that returns the constant), put it in
You can write a forwarder function in C (that returns the constant), put it in
src/main/resources/scala-native/ and then extern that in SN instead
looking into the src to see what scala-native does for its supported libs, I found this:
#include <math.h>
float scalanative_huge_valf() { return HUGE_VALF; }
double scalanative_huge_val() { return HUGE_VAL; }
float scalanative_infinity() { return INFINITY; }
float scalanative_nan() { return NAN; }
int scalanative_math_errhandling() { return math_errhandling; }
int scalanative_math_errno() { return MATH_ERRNO; }
int scalanative_math_errexcept() { return MATH_ERREXCEPT; }Does this mean I'm basically out of luck :D ?
@velvetbaldmime:matrix.org yeah, apparently no way around it.
Yeah, given that defs are inlined and not present in the linked code, SN has nothing to reference really
I would use a forwarder function because of waves hands various #ifdefs for platforms/flags/compiler versions etc.
With a forwarder you don't have to worry that the value will go out of date if you link with different flags/on different platform
With a forwarder you don't have to worry that the value will go out of date if you link with different flags/on different platform
I'm writing a binding generator and the little knowledge I acquired suggests to me that I should not make any assumptions about the values of the constants in large libraries :D
1 reply
Yeah it's pretty horrible, unfortunately. There are a few other gotchas with globals, which actually came up recently when David was trying to write a binding for sqlite, I think: indoorvivants/sn-bindgen#4
I had no idea that
/* Link global variable declared in global.c to this program */
extern int num1, num2;was even a thing, so things like this probably need both setters and getters
With
diverging implicit expansion for type scala.scalanative.unsafe.Tag[T1]
@sealmove Not many people here anymore as we moved to Discord. Hope you can join - https://discord.com/invite/scala
This is the blog post :)
About the first one, if they offer a C api, why not? :)
Hi! I have created a CLI tool that I compiled using scala native. Since I'm pretty new to SN, how would I go about compiling to multiple architectures at once (mac M1, mac Intel, ubuntu Intel,...) with different file names? I'm using the sbt plugin. my repo: https://github.com/leonbur/table
1 reply
No, it doesn't have. You need to create an
You can do it inside your Scala Native module in a
extern "C" block in C++ and export what you need as C functions.You can do it inside your Scala Native module in a
.cpp file inside your resources ( in src/main/resources/scala-native) and they will be compiled and linked in your Scala Native application.
I am glad I joined this amazing community.
You know I was wondering if Scala native is considered systems programming language similar to C, C++ or Rust.
Hey @Ajob41:
Most of the community is at #scala-native:matrix.org (or discord).
Regarding your question, I would say so. There was even a book mentioning that in the title: https://www.amazon.com/Modern-Systems-Programming-Scala-Native/dp/1680506226
The book is pretty outdated by now, though