search for: resourcedir

...gnostics engine. Clang.createDiagnostics(int(CCArgs.size()),const_cast<char**>(CCArgs.data())); if (!Clang.hasDiagnostics()) return 1; // Infer the builtin include path if unspecified. if (Clang.getHeaderSearchOpts().UseBuiltinIncludes && Clang.getHeaderSearchOpts().ResourceDir.empty()) Clang.getHeaderSearchOpts().ResourceDir = CompilerInvocation::GetResourcesPath(argv[0], MainAddr); // Create and execute the frontend to generate an LLVM bitcode module. llvm::OwningPtr<CodeGenAction> Act(new EmitLLVMOnlyAction()); if (!Clang.ExecuteAction(*Act))...

I tried what you said, now I get: LLVM ERROR: Program used external function 'yipee' which could not be resolved! Stack dump: 0. Running pass 'X86 Machine Code Emitter' on function '@main' did not even get as far as a breakpoint. Óscar Fuentes wrote: > > gafferuk <gafferuk at gmail.com> writes: > >> Im confused. The function i wish to call is

...different from builtin header files which can use the preprocessor to internally differentiate their contents based on the target platform. My proposed solution: - Base the path on the shared "resource directory" concept which already exists in Clang. - Builtin header files are at <ResourceDir>/include already. - Append a "base" triple directory name. - Append a "lib" directory name for runtime libraries - Place the runtime libraries as "libcompiler_rt_<sublib>.a" for each sub-library component "<sublib>". Example for "x/bin/cl...

gafferuk <gafferuk at gmail.com> writes: > Im confused. The function i wish to call is a return type of int. > Im calling it with int dd = yipee(1); > > What's wrong? Declare the function: int yipee(int); int main() { int dd = yipee(1); return 0; } If that still crashes, put a breakpoint on `yipee' and see if the execution gets there, if the argument is

...nvocation(CI.take()); // Create the compilers actual diagnostics engine. Clang.createDiagnostics(); if (!Clang.hasDiagnostics()) return 1; // Infer the builtin include path if unspecified. if (Clang.getHeaderSearchOpts().UseBuiltinIncludes && Clang.getHeaderSearchOpts().ResourceDir.empty()) Clang.getHeaderSearchOpts().ResourceDir = CompilerInvocation::GetResourcesPath(argv, MainAddr); // CompilerInvocation::GetResourcesPath(argv[0], MainAddr); // Create and execute the frontend to generate an LLVM bitcode module. OwningPtr<CodeGenAction> Act(new Em...

...r files which can use the > preprocessor to internally differentiate their contents based on the target > platform. > My proposed solution: > - Base the path on the shared "resource directory" concept which already > exists in Clang. >   - Builtin header files are at <ResourceDir>/include already. > - Append a "base" triple directory name. > - Append a "lib" directory name for runtime libraries > - Place the runtime libraries as "libcompiler_rt_<sublib>.a" for each > sub-library component "<sublib>". > Ex...

...preprocessor to internally differentiate their contents based on the > target > > platform. > > My proposed solution: > > - Base the path on the shared "resource directory" concept which already > > exists in Clang. > > - Builtin header files are at <ResourceDir>/include already. > > - Append a "base" triple directory name. > > - Append a "lib" directory name for runtime libraries > > - Place the runtime libraries as "libcompiler_rt_<sublib>.a" for each > > sub-library component "<subli...

...ich can use the > preprocessor to internally differentiate their contents based on the target > platform. > > My proposed solution: > > - Base the path on the shared "resource directory" concept which already > exists in Clang. > - Builtin header files are at <ResourceDir>/include already. > - Append a "base" triple directory name. > - Append a "lib" directory name for runtime libraries > - Place the runtime libraries as "libcompiler_rt_<sublib>.a" for each > sub-library component "<sublib>". > &g...

Makes sense, yeah, trying something in a different environment is usually a good way to find problems. I had indeed moved the renamed clang-cl.exe to a different directory, but when I move it back into its home directory and retry the build, I get the same errors. On Thu, Jun 11, 2015 at 11:16 PM, Reid Kleckner <rnk at google.com> wrote: > Thanks for trying the self-host, it's