Page 1 of 2 12 LastLast
Results 1 to 10 of 15

Thread: Bug: Sencha Cmd 6.0.0.202 Linux not generating CSS

  1. #1

    Default Bug: Sencha Cmd 6.0.0.202 Linux not generating CSS

    Found answer for my own question.
    Details in post #13
    https://www.sencha.com/forum/showthr...=1#post1138933


    I am using Sencha Cmd 6.0.0.202 in both Windows 7 and CentOS 6.
    I found somethings weird in CentOS (or Linux).

    In Windows, if we issue
    sencha app build production
    it will build, compile SCSS and generate the compiled CSS in
    [project root]/build/production/[project name]/classis/resources/[project-name]-all.css
    [project root]/build/production/[project name]/classis/resources/[project-name]-all_1.css
    [project root]/build/production/[project name]/classis/resources/[project-name]-all_2.css

    In Windows, if we issue
    sencha app watch
    it will build, compile SCSS and generate the compiled CSS in
    [project root]/build/development/[project name]/classis/resources/[project-name]-all.css
    [project root]/build/development/[project name]/classis/resources/[project-name]-all_1.css
    [project root]/build/development/[project name]/classis/resources/[project-name]-all_2.css

    However, in CentOS, the story is different
    the CSS is not generated as above location.
    In fact, I have to manually run build production or watch command in Windows and manually copy the generated CSS into CentOS.
    Same project in Windows and CentOS.

    So I suspect is Linux version of Sencha Cmd causes this bug.


    After output using INFO and DEBUG switch, found somethings weird as follow.
    Highlighted in blue color are the difference.

    Windows watch INFO
    Code:
    ... ... ...
    
    [INF] -compile-sass:
    [INF] writing sass content to D:\User\Projects\HttpdProjects\testProj\build\temp\development\testProj\sass\testProj-all.scss.tmp
    [INF] appending sass content to D:\User\Projects\HttpdProjects\testProj\build\temp\development\testProj\sass\testProj-all.scss.tmp
    [INF] appending sass content to D:\User\Projects\HttpdProjects\testProj\build\temp\development\testProj\sass\testProj-all.scss.tmp
    [INF] building sass from D:\User\Projects\HttpdProjects\testProj/build/temp/development/testProj/sass/testProj-all.scss to D:\User\Projects\HttpdProjects\testProj/build/development/testProj/classic/resources/testProj-all.css
    [INF] Compiling D:\User\Projects\HttpdProjects\testProj/build/temp/development/testProj/sass/testProj-all.scss to D:\User\Projects\HttpdProjects\testProj/build/development/testProj/classic/resources/testProj-all.css
    [INF] Using base href : D:\User\Projects\HttpdProjects\testProj/build/development/testProj/classic/resources/
    [INF] Using base href : D:\User\Projects\HttpdProjects\testProj/build/development/testProj/classic/resources/
    [INF] Build complete for ..\..\build\temp\development\testProj\sass\testProj-all.scss
    [INF] Building ..\..\build\temp\development\testProj\sass\testProj-all.scss
    [INF] saving generated css content to D:\User\Projects\HttpdProjects\testProj/build/development/testProj/classic/resources/testProj-all_1.css
    [INF] saving generated css content to D:\User\Projects\HttpdProjects\testProj/build/development/testProj/classic/resources/testProj-all_2.css
    [INF] 
    [INF] -compass-compile-theme-folders:
    [INF] 
    [INF] -compass-compile-sass-dir:
    [INF] 
    [INF] -compass-compile:
    
    ... ... ...

    CentOS watch INFO
    Code:
    ... ... ...
    
    [INF] -compile-sass:
    [INF] writing sass content to /appl/www/testProj/build/temp/development/testProj/sass/testProj-all.scss.tmp
    [INF] appending sass content to /appl/www/testProj/build/temp/development/testProj/sass/testProj-all.scss.tmp
    [INF] appending sass content to /appl/www/testProj/build/temp/development/testProj/sass/testProj-all.scss.tmp
    [INF] building sass from /appl/www/testProj/build/temp/development/testProj/sass/testProj-all.scss to /appl/www/testProj/build/development/testProj/classic/resources/testProj-all.css
    [INF] Compiling /appl/www/testProj/build/temp/development/testProj/sass/testProj-all.scss to /appl/www/testProj/build/development/testProj/classic/resources/testProj-all.css
    [INF]
    [INF] -compass-compile-theme-folders:
    [INF]
    [INF] -compass-compile-sass-dir:
    [INF]
    [INF] -compass-compile:
    
    ... ... ...

    Windows watch DEBUG
    Code:
    ... ... ...
    
    [DBG] received watch key : D:\User\Projects\HttpdProjects\testProj
    [DBG] processing watch key D:\User\Projects\HttpdProjects\testProj
    [DBG] processing watch event ENTRY_MODIFY : D:\User\Projects\HttpdProjects\testProj\bootstrap.css
    [DBG] No WatchSet found for event MODIFIED : D:\User\Projects\HttpdProjects\testProj\bootstrap.css
    [DBG] No WatchSet found for event MODIFIED : D:\User\Projects\HttpdProjects\testProj
    [INF] building sass from D:\User\Projects\HttpdProjects\testProj/build/temp/development/testProj/sass/testProj-all.scss to D:\User\Projects\HttpdProjects\testProj/build/development/testProj/classic/resources/testProj-all.css
    [INF] Compiling D:\User\Projects\HttpdProjects\testProj/build/temp/development/testProj/sass/testProj-all.scss to D:\User\Projects\HttpdProjects\testProj/build/development/testProj/classic/resources/testProj-all.css
    [DBG] input path is D:\User\Projects\HttpdProjects\testProj/build/temp/development/testProj/sass/testProj-all.scss
    [DBG] Absolute location is D:\User\Projects\HttpdProjects\testProj\sass\example
    [DBG] Client 763641ca-e672-4d03-aca8-9d0a98315628 starting sass build for ..\..\build\temp\development\testProj\sass\testProj-all.scss
    [DBG] input path is D:\User\Projects\HttpdProjects\testProj/build/development/testProj/classic/resources/testProj-all.css
    [DBG] Absolute location is D:\User\Projects\HttpdProjects\testProj\sass\example
    [DBG] Sending 1 updates to client 763641ca-e672-4d03-aca8-9d0a98315628
    [DBG] RESPONSE /~sass/updates  200 handled=true
    [DBG] Enabled read interest [email protected]{l(/0:0:0:0:0:0:0:1:52595)<->r(/0:0:0:0:0:0:0:1:1841),d=true,open=true,ishut=false,oshut=false,rb=false,wb=false,w=true,i=1r}-{[email protected],g=HttpGenerator{s=4,h=0,b=0,c=-1},p=HttpParser{s=0,l=14,c=0},r=122}
    
    processing update type : BuildSassFile
    [DBG] filled 0/0
    
    [LOG] Building ..\..\build\temp\development\testProj\sass\testProj-all.scss
    saving generated css
    loading generated css
    [LOG] Using base href : http://localhost:1841/build/development/testProj/classic/resources/
    [LOG] Using base href : http://localhost:1841/build/development/testProj/classic/resources/
    css build complete
    [LOG] Build complete for ..\..\build\temp\development\testProj\sass\testProj-all.scss
    [DBG] filled 376/376
    
    ... ... ...

    CentOS watch DEBUG
    Code:
    ... ... ...
    
    [DBG] received watch key : /appl/www/testProj
    [DBG] processing watch key /appl/www/testProj
    [DBG] processing watch event ENTRY_DELETE : /appl/www/testProj/bootstrap.css
    [DBG] No WatchSet found for event DELETED : /appl/www/testProj/bootstrap.css
    [DBG] processing watch event ENTRY_CREATE : /appl/www/testProj/bootstrap.css
    [DBG] No WatchSet found for event CREATED : /appl/www/testProj/bootstrap.css
    [DBG] processing watch event ENTRY_MODIFY : /appl/www/testProj/bootstrap.css
    [DBG] No WatchSet found for event MODIFIED : /appl/www/testProj/bootstrap.css
    [INF] building sass from /appl/www/testProj/build/temp/development/testProj/sass/testProj-all.scss to /appl/www/testProj/build/development/testProj/classic/resources/testProj-all.css
    [DBG] No WatchSet found for event MODIFIED : /appl/www/testProj
    [INF] Compiling /appl/www/testProj/build/temp/development/testProj/sass/testProj-all.scss to /appl/www/testProj/build/development/testProj/classic/resources/testProj-all.css
    [DBG] queueing build for path /appl/www/testProj/build/temp/development/testProj/sass/testProj-all.scss
    [INF]
    [INF] -compass-compile-theme-folders:
    [INF]
    [INF] -compass-compile-sass-dir:
    [INF]
    [INF] -compass-compile:
    
    ... ... ...

  2. #2
    Sencha Premium User
    Join Date
    Jan 2014
    Location
    Fort Worth, TX, USA
    Posts
    64

    Default

    Where is the enerated CSS being created, if not in the right place?

  3. #3

    Default

    Quote Originally Posted by davmillar View Post
    Where is the enerated CSS being created, if not in the right place?
    It is not generating

  4. #4

    Default

    Added INFO and DEBUG output for both Windows and CentOS

  5. #5
    Sencha - Support Team
    Join Date
    Oct 2011
    Posts
    4,108

    Default

    Have you tried the most recent version of Sencha Cmd 6.0.2.14?

  6. #6

    Default

    Quote Originally Posted by fmoseley View Post
    Have you tried the most recent version of Sencha Cmd 6.0.2.14?
    Thanks for you reply.
    I have tested with 6.0.2.14 in CentOS but still the same, the CSS is not generating.

    p/s: Java version 1.7.0_45

  7. #7
    Sencha - Support Team
    Join Date
    Oct 2011
    Posts
    4,108

    Default

    Is this reproducible with the base application created with sencha generate app?
    What is the exact version of CentOS 6 that you are having this problem? 32 or 64 bit?

  8. #8

    Default

    Quote Originally Posted by fmoseley View Post
    Is this reproducible with the base application created with sencha generate app?
    What is the exact version of CentOS 6 that you are having this problem? 32 or 64 bit?
    Yes, it is reproducible with the base application created with sencha generate app in CentOS.
    After issue sencha generate app, then add some css in .../sass/var/all.scss
    Then run sencha app watch
    The css is not generating in build/development/.../classic/resources

    Java Version:
    java version "1.7.0_45"
    Java(TM) SE Runtime Environment (build 1.7.0_45-b18)
    Java HotSpot(TM) 64-Bit Server VM (build 24.45-b08, mixed mode)

    CentOS Version:
    CentOS release 6.7 (Final)
    Linux XXX 2.6.32-573.7.1.el6.x86_64 #1 SMP Tue Sep 22 22:00:00 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

  9. #9
    Sencha Premium Member
    Join Date
    Mar 2015
    Posts
    2

    Default Sencha Cmd v6.0.2.14 Ubuntu linux almost same

    sencha -sdk ./ext-6.0.1/ generate app test1 ./test1

    [ERR] failed to download path : /home/leesc/mobile-work/test1/ext-6.0.1/packages/core/sass/etc/_all.scss
    ..
    ..
    ..

    ubuntu : VERSION="14.04.3 LTS, Trusty Tahr"
    Linux W65-67SH 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8 10:21:08 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

  10. #10
    Sencha Premium Member
    Join Date
    Mar 2015
    Posts
    2

    Lightbulb Sencha Cmd install option makes differency.

    When installing Sencha Cmd there is an option to select for compnent. If select compass extension, it makes errors for css.

    Screenshot from 2015-11-06 10:07:41.png

    When I did not select compass extension option there is no error in Sencha Cmd generate app...

    This is same for Sencha Cmd version SenchaCmd-6.0.2.14-linux-amd64 and SenchaCmd-6.0.3.33-linux-amd64.

    But if someone still using sass and compass, this must be solved..

Page 1 of 2 12 LastLast

Similar Threads

  1. Replies: 5
    Last Post: 1 Aug 2017, 2:57 PM
  2. not run sencha architect 3 in linux
    By FELIX_LEAL in forum Sencha Architect 3.x: Bugs
    Replies: 7
    Last Post: 9 Dec 2014, 6:52 PM
  3. Sencha CMD on linux 64
    By revolunet in forum Sencha Cmd
    Replies: 4
    Last Post: 2 Jul 2013, 2:37 AM
  4. Sencha 2 command for Linux
    By harsha1485 in forum Sencha Touch 2.x: Q&A
    Replies: 24
    Last Post: 19 Jul 2012, 10:26 AM
  5. Sencha SDK Tools for Linux ?
    By superstructor in forum Sencha Touch 2.x: Discussion
    Replies: 20
    Last Post: 3 Apr 2012, 11:17 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •