[TIMOB-18457] Windows: Cmakelist template generated bad paths for nested folders in Resources
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | None |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2015-01-28T20:03:03.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | n/a |
| Components | Tooling, Windows |
| Labels | n/a |
| Reporter | Christopher Williams |
| Assignee | Christopher Williams |
| Created | 2015-01-28T16:35:40.000+0000 |
| Updated | 2017-03-24T20:51:17.000+0000 |
Description
There's two issues with the generated CMakeLists.txt from our template:
- nested folders are using slashes in the variable name, rather than replacing all slashes with underscores (only the first is getting replaced, not all slashes)
- The incorrect slash is being used to designate the destination relative path inside the app. We need to use '\', but are using '/'.
As a result when we try to build the app in Visual Studio it will complain about being unable to find files that do exist.
To test: 1. You must install the Titanium CLI from the git master branch:
npm install -g git://github.com/appcelerator/titanium.git#master2. You must install Titanium SDK from master:ti sdk install -b master -d3. You must copy the titanium_mobile_windows/templates/build/CMakeLists.txt.ejs from the PR into the SDK/windows/templates/build. 4. Generate an app that has at least two levels of folders deep underneath Resources. (i.e. Resources/alloy/controllers/index.js) I believe the standard alloy two tab app might work here. 5. Runti build -p windows -T wp-emulator -C 8-1-1 --wp-publisher-guid 00000000-0000-1000-8000-000000000000I can successfully build and run an Alloy-based app. I tested using both a single-window app containing just a label, and a single-window app that used
Closing ticket as fixed.