I found the the reason behind the odd behaviour, It's actually normal in my
case as my
*hsOpts*.*ResourceDir* path keeps on changing on every run during Debug
build/run process under Xcode.
*hsOpts*.*ResourceDir *path refers to a bundle inside my app. This is the
reason why I observe normal as odd
No, it doesn't happen. The same flags works fine with swiftc when using
from command line.
swiftc xcode project generated from Ninja have the same issue as I have i.e
hash value is different for each run.
LLVMTest.app is my application that is linked with swift-clang, swift-llvm
& swift-2.2.relea
If the hash value of the module is different then most likely something else is
going on -- are you passing any special flags or defines as part of the
compiler command? If you run the same command from swiftc on the command line
do you see the same behavior?
- Daniel
> On Apr 29, 2016, at 2:
Every-time I run swift frontend the clang creates a new cachedir with
modulecache path hash(on every run the hash value is different for the same
input string) as the name of the dir and generates default cocoa framework
pcm files inside it.
I am using the swift front-end c++ api's to compile a si
Clang will cache these automatically, can you give more details on exactly what
you are seeing?
- Daniel
> On Apr 28, 2016, at 10:50 PM, Ramakrishna Mallireddy via swift-users
> wrote:
>
> I have these precompiled module files generated every-time I run the swift
> compiler.
>
> _Builtin_s
