[TIMOB-23251] Windows: Modules do not build with 'appc run'
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Critical |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2016-04-21T14:51:08.000+0000 |
| Affected Version/s | Release 5.2.0 |
| Fix Version/s | Release 5.4.0 |
| Components | Windows |
| Labels | n/a |
| Reporter | Gary Mathews |
| Assignee | Gary Mathews |
| Created | 2016-04-20T20:03:20.000+0000 |
| Updated | 2016-06-27T19:17:06.000+0000 |
Description
Modules do not build when using
appc run
appc new -t timodule -n module --id com.win.module
cd module\windows
appc run -p windows --build-only
PR: https://github.com/appcelerator/titanium_mobile_windows/pull/640
Kota, with what I had in the 20160420, can I use that to test the background service even if this do not work the way you anticipated? I have created a module with the "old" way I told you and compiled and used it in the app, but now I want to extend it with the backgrund task, will this work or not in that SDK? Or do I have to wait for more features that go into the SDK? Also, is it not possible to make sure the module create and background service with push callback as well go into 5.3.0 GA?
Verified using: Windows 10 Pro Ti SDK: 5.4.0.v20160617074028 Appc NPM: 4.2.7-2 Appc CLI: 5.4.0-18 Modules can now be built using
appc run \-p windows \-\-build-onlyfrom within the<module>\windowsfolder or when the<module>\windowsfolder is passed in using\-\-project-dir. Filed TIMOB-23563 regarding the EventEmitter memory leak warning when building. Closing ticket