albertgao
04/12/2018, 12:58 AMspierce7
04/12/2018, 3:32 PMagrosner
04/12/2018, 4:36 PMAtomicReference
sdeleuze
04/12/2018, 7:38 PMagrosner
04/14/2018, 1:28 PMjo
04/14/2018, 4:44 PMjkbbwr
04/17/2018, 1:37 AMmolikto
04/17/2018, 9:36 AManidotnet
04/20/2018, 12:21 PMlouiscad
04/20/2018, 12:48 PMspierce7
04/20/2018, 6:23 PMrellenberger
04/20/2018, 7:23 PMoleksiyp
04/21/2018, 7:11 PMsdeleuze
04/22/2018, 1:12 PMsdeleuze
04/22/2018, 5:58 PMdevbridie
04/23/2018, 3:52 AMprintln
. I'm using gradle according to https://github.com/JetBrains/kotlin-native/blob/master/GRADLE_PLUGIN.md .Jason Miesionczek
04/23/2018, 2:45 PMheaders fuse3/fuse_lowlevel.h
compilerOpts = -lfuse3
when i run cinterop as such: cinterop -def libfuse.def -copt -I/usr/include -o libfuse
I get this error:
Exception in thread "main" java.lang.Error: /usr/include/fuse3/fuse_lowlevel.h:22:2: error: FUSE_USE_VERSION not defined
at org.jetbrains.kotlin.native.interop.indexer.UtilsKt.ensureNoCompileErrors(Utils.kt:137)
at org.jetbrains.kotlin.native.interop.indexer.IndexerKt.indexDeclarations(Indexer.kt:898)
at org.jetbrains.kotlin.native.interop.indexer.IndexerKt.buildNativeIndexImpl(Indexer.kt:888)
at org.jetbrains.kotlin.native.interop.indexer.NativeIndexKt.buildNativeIndex(NativeIndex.kt:56)
at org.jetbrains.kotlin.native.interop.gen.jvm.MainKt.processCLib(main.kt:307)
at org.jetbrains.kotlin.native.interop.gen.jvm.MainKt.interop(main.kt:38)
at org.jetbrains.kotlin.cli.utilities.InteropCompilerKt.invokeInterop(InteropCompiler.kt:100)
at org.jetbrains.kotlin.cli.utilities.MainKt.main(main.kt:29)
This is normal when a #define FUSE_USE_VERSION 31
does not appear before the header is included. Is there anyway I can do this? I tried adding the ---
and putting the define after that, but the docs indicate that this is for adding stuff AFTER the headers have been processed. Is there a way to add something before the headers?keith
04/23/2018, 4:36 PMkhairil.ushan
04/24/2018, 7:34 PMThe feature "multi platform projects" is experimental and should be enabled explicitly
khairil.ushan
04/24/2018, 7:42 PMspierce7
04/25/2018, 3:52 AMLeonid Popescu
04/25/2018, 9:00 AMinterface SomeInterface {
var aProperty: String
}
the generated ObjC interface would be
@protocol AIKSomeInterface
@required
@property NSString* aProperty;
@end;
and implementing it, with setters and getters in ObjC is not allowed because it’s seen as atomic
, if my class declares the property as @property (nonatomic) NSString* aProperty;
then it shows warnings that atomicity is not the same as in protocol.
can we ignore it for now or better just to use functions for getters and setters instead of properties ?yusuf3000
04/25/2018, 1:03 PMerror: cannot access 'UpdateBookingCommandAction': it is internal in 'com.framework.action'
assertEquals(action.booking.latitude, 0.toDouble())
I remember seeing a bug report for it, I was wondering if there is a fix for this yet?
The unit tests run fine when testing on android platform.fitzoh
04/27/2018, 4:44 PMspierce7
04/28/2018, 4:47 AMspierce7
04/28/2018, 9:50 PMbrabo-hi
04/30/2018, 1:57 AMSam
04/30/2018, 6:08 AMlipo
to glue them together. Previously I was able to just reference both framework versions in my project but something must have changed with either 0.7
or Xcode 9.3 as I started to get architecture related build errors. My current solution is to invoke a shell script that creates the framework directory, uses lipo to glue the two architectures together and then copies over the header and module map.molikto
04/30/2018, 7:55 AMsendilkumarn [JHipster]
04/30/2018, 2:41 PM