Skip to content

Modify the build method of TizenRT target #2164

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 16, 2018

Conversation

rtakacs
Copy link
Contributor

@rtakacs rtakacs commented Jan 9, 2018

Introduced a cmake/toolchain_mcu_artik053.cmake file that defines all the target specific compiler options.

Modified the Makefile.tizenrt to do not copy the created static libraries to the TizenRT folder. Instead, the application builder Makefile (tizenrt-artik053/apps/jerryscript/Makefile) copies the
required static libraries to TizenRT.

This modification helps to build JerryScript with the Python based build-script. In this case the user can use more build options.

tools/build.py \
    --clean \
    --lto=OFF \
    --jerry-cmdline=OFF \
    --all-in-one=OFF \
    --jerry-libc=OFF \
    --mem-heap=70 \
    --profile=es2015-subset \
    --toolchain=${PWD}/cmake/toolchain_mcu_artik053.cmake \
    --compile-flag="--sysroot=${PWD}/../TizenRT/os"

@rtakacs
Copy link
Contributor Author

rtakacs commented Jan 10, 2018

Note: the patch also removes unused/unnecessary codes.

@robertsipka
Copy link
Contributor

robertsipka commented Jan 10, 2018

Nice patch! Could you please also update the README with the followings:

  1. Extend the description of the JerryScript build method with the Python based build-script.
  2. akosthekiss mentioned a few request in Outdated or incorrect build instructions for several targets #2103:
  • The README suggest to checkout the 1.1_Public_Release branch of the TizenRT. Please write there that it is the last known working version (and the romfs patch is needed).
  • The PPA-based GCC6 version works also, the GCC4.9 is a lower bound. Please update it accordingly.

LGTM (informally) after these minor fixes.

@glistening
Copy link
Contributor

@robertsipka I already updated for second item in #2128.

@robertsipka
Copy link
Contributor

@glistening : Indeed, I missed that, thanks.

Introduced a cmake/toolchain_mcu_artik053.cmake file that defines
all the target specific compiler options.

Modified the Makefile.tizenrt to do not copy the created static
libraries to the TizenRT folder. Instead, the application builder
Makefile (tizenrt-artik053/apps/jerryscript/Makefile) copies the
required static libraries to TizenRT.

JerryScript-DCO-1.0-Signed-off-by: Roland Takacs [email protected]
@rtakacs rtakacs force-pushed the tizenrt-toolchain-file branch from 5ac7ea3 to 9652424 Compare January 12, 2018 08:59
@rtakacs
Copy link
Contributor Author

rtakacs commented Jan 12, 2018

@robertsipka I've updated the README.md according to your requirements.

@rtakacs
Copy link
Contributor Author

rtakacs commented Jan 12, 2018

@hs0225 Could you try out this PR on ARTIK053?

@glistening
Copy link
Contributor

@rtakacs I would like to specify the requirement of "trying out this PR by @hs0225"? Because perhaps you already build and test jerryscript with this PR on ARTIK053. Do you want a cross check?

@rtakacs
Copy link
Contributor Author

rtakacs commented Jan 15, 2018

@glistening Yes, I've already tested this PR on ARTIK053 (just build and flash, and run jerry with no test). It worked for me, so maybe it's enough just to check the modifications.
(Travis is also green, so probably everything is OK :))

@glistening
Copy link
Contributor

glistening commented Jan 16, 2018

LGTM (as a maintainer of TizenRT port)

@yichoi
Copy link
Contributor

yichoi commented Jan 16, 2018

LGTM

@yichoi yichoi merged commit 680bafd into jerryscript-project:master Jan 16, 2018
@rtakacs rtakacs deleted the tizenrt-toolchain-file branch January 18, 2019 14:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants