Skip to content

Would you release app for Windows (32bit)? #88

Description

@linpengcheng

Description

[Would you release app for Windows (32bit)?]

Versions

  • Mark Text: 0.8.12
  • OS: windows 7 (32 bit)

Activity

  1. SuperSandro2000 commented on Mar 28, 2018

    @SuperSandro2000
    Contributor

    Is there even a Windows version that does not have x64?
    Win10 comes only x64 and 8 was almost only sold with x64. Win 7 should be mostly x64 and XP is EOL.
    Maybe some Ultrabooks use x86.

  2. linpengcheng commented on Mar 28, 2018

    @linpengcheng
    Author

    Many Win7 x86 are upgraded from XP x86, Win7 x86 users should be more than x64, of course, the programmer group x64 more。Enterprise development, many programmers also want to support x86, so use x86

  3. Jocs commented on Mar 28, 2018

    @Jocs
    Member

    @linpengcheng I think you are right, Can you help and create a PR to support (32bit)?

  4. Jocs commented on Mar 28, 2018

    @Jocs
    Member

    @notAlaanor help wanted. 🎁

  5. notAlaanor commented on Mar 29, 2018

    @notAlaanor
    Contributor

    Is there a problem compiling an x86 version? It should work as far as I know.

  6. Jocs commented on Mar 29, 2018

    @Jocs
    Member

    @linpengcheng saied:

    Many Win7 x86 are upgraded from XP x86, Win7 x86 users should be more than x64, of course, the programmer group x64 more。Enterprise development, many programmers also want to support x86, so use x86

  7. fxha commented on Mar 29, 2018

    @fxha
    Contributor

    @Jocs We cannot generate x86 and x86_64 nsis setups at the same time because they override itself. We can add a new build script target like "release:win32": "node .electron-vue/build.js && electron-builder --win --ia32", so that you can build the x86 nsis setup, rename it and generate all other packages.

    If you build both ia32 and x64 arch (--x64 --ia32), you in any case get one installer.

  8. linpengcheng commented on Mar 29, 2018

    @linpengcheng
    Author

    npm install fail:
    npm ERR! path D:\marktext\build
    npm ERR! code EISDIR
    npm ERR! errno -4068
    npm ERR! syscall open
    npm ERR! EISDIR: illegal operation on a directory, open 'D:\marktext\build'

    npm run build fail, many error like:
    ERROR in ./node_modules/css-loader?minimize!./node_modules/vue-loader/lib/style-compiler?{"optionsId":"0","vue":true,"id":"data-v-3f505bc2","scoped":true,"sourceMap":false}!./node_modules/vue-loader/lib/selector.js?type=styles&index=0!./src/renderer/components/aidou/loading.vue
    Module build failed: BrowserslistError: Unknown browser query basedir=$(dirname "$(echo "$0" | sed -e 's,\\,/,g')")
    at error (D:\marktext\node_modules\caniuse-api\node_modules\browserslist\index.js:37:11)
    at D:\marktext\node_modules\caniuse-api\node_modules\browserslist\index.js:222:9
    at Array.forEach ()
    at browserslist (D:\marktext\node_modules\caniuse-api\node_modules\browserslist\index.js:196:13)
    at cleanBrowsersList (D:\marktext\node_modules\caniuse-api\dist\utils.js:56:59)
    at setBrowserScope (D:\marktext\node_modules\caniuse-api\dist\index.js:29:43)
    at Object. (D:\marktext\node_modules\caniuse-api\dist\index.js:91:1)
    at Module._compile (module.js:649:30)
    at Object.Module._extensions..js (module.js:660:10)
    at Module.load (module.js:561:32)
    at tryModuleLoad (module.js:501:12)
    at Function.Module._load (module.js:493:3)
    at Module.require (module.js:593:17)
    at require (internal/module.js:11:18)
    at Object. (D:\marktext\node_modules\postcss-merge-rules\dist\lib\ensureCompatibility.js:7:19)
    at Module._compile (module.js:649:30)
    at Object.Module._extensions..js (module.js:660:10)
    at Module.load (module.js:561:32)
    at tryModuleLoad (module.js:501:12)
    at Function.Module._load (module.js:493:3)
    at Module.require (module.js:593:17)
    at require (internal/module.js:11:18)

    npm ERR! code ELIFECYCLE
    npm ERR! errno 1
    npm ERR! [email protected] build: node .electron-vue/build.js && electron-builder
    npm ERR! Exit status 1
    npm ERR!
    npm ERR! Failed at the [email protected] build script.
    npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

  9. SuperSandro2000 commented on Mar 29, 2018

    @SuperSandro2000
    Contributor

    You run just the command above right?
    It is not that easy

  10. linpengcheng commented on Mar 29, 2018

    @linpengcheng
    Author

    I've been running "npm install" a lot. then run "npm run build"


    If you wish to build Mark Text yourself:

    first clone this repo.
    Run npm install
    Run npm run build
    copy the build app to Applications folder, or if on Windows run the executable installer.

  11. fxha commented on Mar 29, 2018

    @fxha
    Contributor

    Windows installation instructions

    First of all install nodejs and git.

    Open cmd.exe and go to marktext source folder - there must be a package.json file. Then run:

    1. npm install - this might take a while
    2. npm run build
    3. Mark Text setup is located under build or usebuild\win-ia32-unpacked folder - have fun
  12. added 2 commits that reference this issue on Mar 31, 2018
    e942da5
    b57ae88
  13. added a commit that references this issue on Jun 21, 2026
    afd7ff7
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions