Added MesonExporter.ts
#64
Conversation
RobDangerous
left a comment
RobDangerous
left a comment
There was a problem hiding this comment.
Just some nitpicks to address. But I like this and want kmake to build bridges to similar tools.
kmake/src/Project.ts
Outdated
| systemDependendLibraries: any; | ||
| includes: {file: string, options: any}[]; | ||
| excludes: string[]; | ||
| subprojects: string[]; |
There was a problem hiding this comment.
We do already have Project.subProjects.
There was a problem hiding this comment.
My bad, I forgot to remove this as I was referencing mainly the CMakeExporter.ts and didn't seesubProjects as at the time of development, I had my vim search to consider whether the character was capital or lowercase.
package.json
Outdated
| @@ -0,0 +1,5 @@ | |||
| { | |||
| "dependencies": { | |||
| "typescript": "^5.8.3" | |||
There was a problem hiding this comment.
The package.json file (that has typescript as a devDependency) is in the kmake subdirectory.
|
I removed the nitpicks, at least I think I did. |
Almost :) The subprojects element still exists (the "Files changed" tab is convenient for checking the end result of a pull request). |
|
That is very idiotic of me, I'm so sorry! I can't believe I forgot to remove it. |
|
Please don't get worked up about a simple oversight and... thank you very much! |
2 participants
This is extremely useful for my projects that use Kore V2 or V3, in which I want to support other libraries that rely on CMake or Meson build scripts. The Meson Exporter doesn't create an entire project; it just generates the needed arguments, include directories, and source files required for C, C++, and/or ObjC, which I use as a sub-directory for my main
meson.build.