Skip to content
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.

Sign up for GitHub

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

Jump to bottom

wish: version release #1726

Closed
rzr opened this issue Aug 13, 2018 · 1 comment
Closed

wish: version release #1726

rzr opened this issue Aug 13, 2018 · 1 comment
Labels
question

Comments

@rzr
Copy link
Contributor

rzr commented Aug 13, 2018

Hi,

Dear iotjs team,

Is there a new release planned soon ?
If not, may I suggested this.

The reason is that current master branch has really improved support for Tizen:Rt (which currently ship a snapshot before 1.0) since some downstream changes have been upstreamed.. so I guess it is valuable to upgrade snapshot in TizenRt.

Relate-to:

Samsung/TizenRT#2018 (comment)

Again this is just a suggestion, I don't want to change any plans.

Samsung/TizenRT#2018 (comment)
rzr added a commit to TizenTeam/iotjs that referenced this issue Aug 29, 2018
@rzr
tizenrt: Relocate downstream Makefile to config dir (along Kconfig)
043a0a7 
[Philippe Coval]

After some (recent) refactoring in build script,
This file was over imported iotjs module in TizenRT.

Like done previously with Kconfig file,
it will be better to minimize downstream patches.

One benefit to have those build related files,
is that then IoT.js can be upgraded into TizenRT
by just cloning iotjs's again into subdir:
TizenRT/external/iotjs

Note: Extra minor changes has been done over TizenRT's patch
to make some options overridable from env var (profile file...)

[Sunghan Chang]

Makefile: move IoT.js-specific build step to IoT.js folder

Because Makefile.unix has TizenRT-common build step,
it is not good including IoT.js-specific step.
Let's add Makefile in IoT.js and execute all of step in it.

Thanks-to: sunghan-chang <sh924.chang@samsung.com>
Change-Id: Iddeb272dc6ad6c283ccad9f92bf02754f9ba3240
Bug-TizenRT: Samsung/TizenRT#2111
Origin: Samsung/TizenRT@bbd3cdb
Relate-to: jerryscript-project#1726
Forwarded: https://github.com/Samsung/iotjs
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
@rzr rzr mentioned this issue Aug 29, 2018
Closed
rzr added a commit to TizenTeam/iotjs that referenced this issue Aug 29, 2018
@rzr
tizenrt: Relocate downstream Makefile to config dir (along Kconfig)
aec2d20 
[Philippe Coval]

After some (recent) refactoring in build script,
This file was over imported iotjs module in TizenRT.

Like done previously with Kconfig file,
it will be better to minimize downstream patches.

One benefit to have those build related files,
is that then IoT.js can be upgraded into TizenRT
by just cloning iotjs's again into subdir:
TizenRT/external/iotjs

Note: Extra minor changes has been done over TizenRT's patch
to make some options overridable from env var (profile file...)

[Sunghan Chang]

Makefile: move IoT.js-specific build step to IoT.js folder

Because Makefile.unix has TizenRT-common build step,
it is not good including IoT.js-specific step.
Let's add Makefile in IoT.js and execute all of step in it.

Thanks-to: sunghan-chang <sh924.chang@samsung.com>
Change-Id: Iddeb272dc6ad6c283ccad9f92bf02754f9ba3240
Bug-TizenRT: Samsung/TizenRT#2111
Origin: Samsung/TizenRT@bbd3cdb
Relate-to: jerryscript-project#1726
Forwarded: jerryscript-project#1732
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
@daeyeon
Copy link
Member

daeyeon commented Aug 30, 2018

We do encourage suggestions for IoT.js but do not guarantee IoT.js which each individual applies to external projects. And, its acceptance is beyond our jurisdiction.

#1732 can answer your query about the plan. A selected version of the platform is applied to our CI before a release. That's for post-maintenance and would be the same for next release.

@daeyeon daeyeon closed this as completed Aug 31, 2018
rzr added a commit to TizenTeam/iotjs that referenced this issue Sep 18, 2018
@rzr
tizenrt: Relocate downstream Makefile to config dir (along Kconfig)
83dd341 
[Philippe Coval]

After some (recent) refactoring in build script,
This file was over imported iotjs module in TizenRT.

Like done previously with Kconfig file,
it will be better to minimize downstream patches.

One benefit to have those build related files,
is that then IoT.js can be upgraded into TizenRT
by just cloning iotjs's again into subdir:
TizenRT/external/iotjs

Note: Extra minor changes has been done over TizenRT's patch
to make some options overridable from env var (profile file...)

[Sunghan Chang]

Makefile: move IoT.js-specific build step to IoT.js folder

Because Makefile.unix has TizenRT-common build step,
it is not good including IoT.js-specific step.
Let's add Makefile in IoT.js and execute all of step in it.

Thanks-to: sunghan-chang <sh924.chang@samsung.com>
Change-Id: Iddeb272dc6ad6c283ccad9f92bf02754f9ba3240
Bug-TizenRT: Samsung/TizenRT#2111
Origin: Samsung/TizenRT@bbd3cdb
Relate-to: jerryscript-project#1726
Forwarded: jerryscript-project#1732
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
rzr added a commit to TizenTeam/iotjs that referenced this issue Sep 18, 2018
@rzr
tizenrt: Relocate downstream Makefile to config dir (along Kconfig)
3eb4bbc 
[Philippe Coval]

After some (recent) refactoring in build script,
This file was over imported iotjs module in TizenRT.

Like done previously with Kconfig file,
it will be better to minimize downstream patches.

One benefit to have those build related files,
is that then IoT.js can be upgraded into TizenRT
by just cloning iotjs's again into subdir:
TizenRT/external/iotjs

Note: Extra minor changes has been done over TizenRT's patch
to make some options overridable from env var (profile file...)

[Sunghan Chang]

Makefile: move IoT.js-specific build step to IoT.js folder

Because Makefile.unix has TizenRT-common build step,
it is not good including IoT.js-specific step.
Let's add Makefile in IoT.js and execute all of step in it.

Thanks-to: sunghan-chang <sh924.chang@samsung.com>
Change-Id: Iddeb272dc6ad6c283ccad9f92bf02754f9ba3240
Bug-TizenRT: Samsung/TizenRT#2111
Origin: Samsung/TizenRT@bbd3cdb
Relate-to: jerryscript-project#1726
Forwarded: jerryscript-project#1732
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
rzr added a commit to TizenTeam/iotjs that referenced this issue Sep 18, 2018
@rzr
tizenrt: Relocate downstream Makefile to config dir (along Kconfig)
2a315de 
[Philippe Coval]

After some (recent) refactoring in build script,
This file was over imported iotjs module in TizenRT.

Like done previously with Kconfig file,
it will be better to minimize downstream patches.

One benefit to have those build related files,
is that then IoT.js can be upgraded into TizenRT
by just cloning iotjs's again into subdir:
TizenRT/external/iotjs

Note: Extra minor changes has been done over TizenRT's patch
to make some options overridable from env var (profile file...)

[Sunghan Chang]

Makefile: move IoT.js-specific build step to IoT.js folder

Because Makefile.unix has TizenRT-common build step,
it is not good including IoT.js-specific step.
Let's add Makefile in IoT.js and execute all of step in it.

Thanks-to: sunghan-chang <sh924.chang@samsung.com>
Change-Id: Iddeb272dc6ad6c283ccad9f92bf02754f9ba3240
Bug-TizenRT: Samsung/TizenRT#2111
Origin: Samsung/TizenRT@bbd3cdb
Relate-to: jerryscript-project#1726
Forwarded: jerryscript-project#1732
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
rzr added a commit to TizenTeam/iotjs that referenced this issue Sep 18, 2018
@rzr
tizenrt: Relocate downstream Makefile to config dir (along Kconfig)
fcf7b32 
[Philippe Coval]

After some (recent) refactoring in build script,
This file was over imported iotjs module in TizenRT.

Like done previously with Kconfig file,
it will be better to minimize downstream patches.

One benefit to have those build related files,
is that then IoT.js can be upgraded into TizenRT
by just cloning iotjs's again into subdir:
TizenRT/external/iotjs

Note: Extra minor changes has been done over TizenRT's patch
to make some options overridable from env var (profile file...)

[Sunghan Chang]

Makefile: move IoT.js-specific build step to IoT.js folder

Because Makefile.unix has TizenRT-common build step,
it is not good including IoT.js-specific step.
Let's add Makefile in IoT.js and execute all of step in it.

Thanks-to: sunghan-chang <sh924.chang@samsung.com>
Change-Id: Iddeb272dc6ad6c283ccad9f92bf02754f9ba3240
Bug-TizenRT: Samsung/TizenRT#2111
Origin: Samsung/TizenRT@bbd3cdb
Relate-to: jerryscript-project#1726
Forwarded: jerryscript-project#1732
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
rzr added a commit to TizenTeam/iotjs that referenced this issue Sep 18, 2018
@rzr
tizenrt: Relocate downstream Makefile to config dir (along Kconfig)
6ccc53a 
[Philippe Coval]

After some (recent) refactoring in build script,
This file was over imported iotjs module in TizenRT.

Like done previously with Kconfig file,
it will be better to minimize downstream patches.

One benefit to have those build related files,
is that then IoT.js can be upgraded into TizenRT
by just cloning iotjs's again into subdir:
TizenRT/external/iotjs

Note: Extra minor changes has been done over TizenRT's patch
to make some options overridable from env var (profile file...)

[Sunghan Chang]

Makefile: move IoT.js-specific build step to IoT.js folder

Because Makefile.unix has TizenRT-common build step,
it is not good including IoT.js-specific step.
Let's add Makefile in IoT.js and execute all of step in it.

Thanks-to: sunghan-chang <sh924.chang@samsung.com>
Change-Id: Iddeb272dc6ad6c283ccad9f92bf02754f9ba3240
Bug-TizenRT: Samsung/TizenRT#2111
Origin: Samsung/TizenRT@bbd3cdb
Relate-to: jerryscript-project#1726
Forwarded: jerryscript-project#1732
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
rzr added a commit to TizenTeam/iotjs that referenced this issue Sep 18, 2018
@rzr
tizenrt: Relocate downstream Makefile to config dir (along Kconfig)
2b96e4c 
[Philippe Coval]

After some (recent) refactoring in build script,
This file was over imported iotjs module in TizenRT.

Like done previously with Kconfig file,
it will be better to minimize downstream patches.

One benefit to have those build related files,
is that then IoT.js can be upgraded into TizenRT
by just cloning iotjs's again into subdir:
TizenRT/external/iotjs

Note: Extra minor changes has been done over TizenRT's patch
to make some options overridable from env var (profile file...)

[Sunghan Chang]

Makefile: move IoT.js-specific build step to IoT.js folder

Because Makefile.unix has TizenRT-common build step,
it is not good including IoT.js-specific step.
Let's add Makefile in IoT.js and execute all of step in it.

Thanks-to: sunghan-chang <sh924.chang@samsung.com>
Change-Id: Iddeb272dc6ad6c283ccad9f92bf02754f9ba3240
Bug-TizenRT: Samsung/TizenRT#2111
Origin: Samsung/TizenRT@bbd3cdb
Relate-to: jerryscript-project#1726
Forwarded: jerryscript-project#1732
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
rzr added a commit to TizenTeam/iotjs that referenced this issue Sep 18, 2018
@rzr
tizenrt: Relocate downstream Makefile to config dir (along Kconfig)
f3a6be3 
[Philippe Coval]

After some (recent) refactoring in build script,
This file was over imported iotjs module in TizenRT.

Like done previously with Kconfig file,
it will be better to minimize downstream patches.

One benefit to have those build related files,
is that then IoT.js can be upgraded into TizenRT
by just cloning iotjs's again into subdir:
TizenRT/external/iotjs

Note: Extra minor changes has been done over TizenRT's patch
to make some options overridable from env var (profile file...)

[Sunghan Chang]

Makefile: move IoT.js-specific build step to IoT.js folder

Because Makefile.unix has TizenRT-common build step,
it is not good including IoT.js-specific step.
Let's add Makefile in IoT.js and execute all of step in it.

Thanks-to: sunghan-chang <sh924.chang@samsung.com>
Change-Id: Iddeb272dc6ad6c283ccad9f92bf02754f9ba3240
Bug-TizenRT: Samsung/TizenRT#2111
Origin: Samsung/TizenRT@bbd3cdb
Relate-to: jerryscript-project#1726
Forwarded: jerryscript-project#1732
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
rzr added a commit to TizenTeam/iotjs that referenced this issue Sep 18, 2018
@rzr
tizenrt: Relocate downstream Makefile to config dir (along Kconfig)
75ba804 
[Philippe Coval]

After some (recent) refactoring in build script,
This file was over imported iotjs module in TizenRT.

Like done previously with Kconfig file,
it will be better to minimize downstream patches.

One benefit to have those build related files,
is that then IoT.js can be upgraded into TizenRT
by just cloning iotjs's again into subdir:
TizenRT/external/iotjs

Note: Extra minor changes has been done over TizenRT's patch
to make some options overridable from env var (profile file...)

[Sunghan Chang]

Makefile: move IoT.js-specific build step to IoT.js folder

Because Makefile.unix has TizenRT-common build step,
it is not good including IoT.js-specific step.
Let's add Makefile in IoT.js and execute all of step in it.

Thanks-to: sunghan-chang <sh924.chang@samsung.com>
Change-Id: Iddeb272dc6ad6c283ccad9f92bf02754f9ba3240
Bug-TizenRT: Samsung/TizenRT#2111
Origin: Samsung/TizenRT@bbd3cdb
Relate-to: jerryscript-project#1726
Forwarded: jerryscript-project#1732
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
rzr added a commit to TizenTeam/iotjs that referenced this issue Sep 18, 2018
@rzr
tizenrt: Relocate downstream Makefile to config dir (along Kconfig)
0743da8 
[Philippe Coval]

After some (recent) refactoring in build script,
This file was over imported iotjs module in TizenRT.

Like done previously with Kconfig file,
it will be better to minimize downstream patches.

One benefit to have those build related files,
is that then IoT.js can be upgraded into TizenRT
by just cloning iotjs's again into subdir:
TizenRT/external/iotjs

Note: Extra minor changes has been done over TizenRT's patch
to make some options overridable from env var (profile file...)

[Sunghan Chang]

Makefile: move IoT.js-specific build step to IoT.js folder

Because Makefile.unix has TizenRT-common build step,
it is not good including IoT.js-specific step.
Let's add Makefile in IoT.js and execute all of step in it.

Thanks-to: sunghan-chang <sh924.chang@samsung.com>
Change-Id: Iddeb272dc6ad6c283ccad9f92bf02754f9ba3240
Bug-TizenRT: Samsung/TizenRT#2111
Origin: Samsung/TizenRT@bbd3cdb
Relate-to: jerryscript-project#1726
Forwarded: jerryscript-project#1732
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
rzr added a commit to TizenTeam/iotjs that referenced this issue Sep 18, 2018
@rzr
tizenrt: Relocate downstream Makefile to config dir (along Kconfig)
a615621 
[Philippe Coval]

After some (recent) refactoring in build script,
This file was over imported iotjs module in TizenRT.

Like done previously with Kconfig file,
it will be better to minimize downstream patches.

One benefit to have those build related files,
is that then IoT.js can be upgraded into TizenRT
by just cloning iotjs's again into subdir:
TizenRT/external/iotjs

Note: Extra minor changes has been done over TizenRT's patch
to make some options overridable from env var (profile file...)

[Sunghan Chang]

Makefile: move IoT.js-specific build step to IoT.js folder

Because Makefile.unix has TizenRT-common build step,
it is not good including IoT.js-specific step.
Let's add Makefile in IoT.js and execute all of step in it.

Thanks-to: sunghan-chang <sh924.chang@samsung.com>
Change-Id: Iddeb272dc6ad6c283ccad9f92bf02754f9ba3240
Bug-TizenRT: Samsung/TizenRT#2111
Origin: Samsung/TizenRT@bbd3cdb
Relate-to: jerryscript-project#1726
Forwarded: jerryscript-project#1732
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
rzr added a commit to TizenTeam/iotjs that referenced this issue Sep 18, 2018
@rzr
tizenrt: Relocate downstream Makefile to config dir (along Kconfig)
349e49a 
[Philippe Coval]

After some (recent) refactoring in build script,
This file was over imported iotjs module in TizenRT.

Like done previously with Kconfig file,
it will be better to minimize downstream patches.

One benefit to have those build related files,
is that then IoT.js can be upgraded into TizenRT
by just cloning iotjs's again into subdir:
TizenRT/external/iotjs

Note: Extra minor changes has been done over TizenRT's patch
to make some options overridable from env var (profile file...)

[Sunghan Chang]

Makefile: move IoT.js-specific build step to IoT.js folder

Because Makefile.unix has TizenRT-common build step,
it is not good including IoT.js-specific step.
Let's add Makefile in IoT.js and execute all of step in it.

Thanks-to: sunghan-chang <sh924.chang@samsung.com>
Change-Id: Iddeb272dc6ad6c283ccad9f92bf02754f9ba3240
Bug-TizenRT: Samsung/TizenRT#2111
Origin: Samsung/TizenRT@bbd3cdb
Relate-to: jerryscript-project#1726
Forwarded: jerryscript-project#1732
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
rzr added a commit to TizenTeam/iotjs that referenced this issue Sep 18, 2018
@rzr
tizenrt: Relocate downstream Makefile to config dir (along Kconfig)
fede0f2 
[Philippe Coval]

After some (recent) refactoring in build script,
This file was over imported iotjs module in TizenRT.

Like done previously with Kconfig file,
it will be better to minimize downstream patches.

One benefit to have those build related files,
is that then IoT.js can be upgraded into TizenRT
by just cloning iotjs's again into subdir:
TizenRT/external/iotjs

Note: Extra minor changes has been done over TizenRT's patch
to make some options overridable from env var (profile file...)

[Sunghan Chang]

Makefile: move IoT.js-specific build step to IoT.js folder

Because Makefile.unix has TizenRT-common build step,
it is not good including IoT.js-specific step.
Let's add Makefile in IoT.js and execute all of step in it.

Thanks-to: sunghan-chang <sh924.chang@samsung.com>
Change-Id: Iddeb272dc6ad6c283ccad9f92bf02754f9ba3240
Bug-TizenRT: Samsung/TizenRT#2111
Origin: Samsung/TizenRT@bbd3cdb
Relate-to: jerryscript-project#1726
Forwarded: jerryscript-project#1732
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
rzr added a commit to TizenTeam/iotjs that referenced this issue Sep 18, 2018
@rzr
tizenrt: Relocate downstream Makefile to config dir (along Kconfig)
bfc461f 
[Philippe Coval]

After some (recent) refactoring in build script,
This file was over imported iotjs module in TizenRT.

Like done previously with Kconfig file,
it will be better to minimize downstream patches.

One benefit to have those build related files,
is that then IoT.js can be upgraded into TizenRT
by just cloning iotjs's again into subdir:
TizenRT/external/iotjs

Note: Extra minor changes has been done over TizenRT's patch
to make some options overridable from env var (profile file...)

[Sunghan Chang]

Makefile: move IoT.js-specific build step to IoT.js folder

Because Makefile.unix has TizenRT-common build step,
it is not good including IoT.js-specific step.
Let's add Makefile in IoT.js and execute all of step in it.

Thanks-to: sunghan-chang <sh924.chang@samsung.com>
Change-Id: Iddeb272dc6ad6c283ccad9f92bf02754f9ba3240
Bug-TizenRT: Samsung/TizenRT#2111
Origin: Samsung/TizenRT@bbd3cdb
Relate-to: jerryscript-project#1726
Forwarded: jerryscript-project#1732
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
rzr added a commit to TizenTeam/iotjs that referenced this issue Sep 18, 2018
@rzr
tizenrt: Relocate downstream Makefile to config dir (along Kconfig)
b01846d 
[Philippe Coval]

After some (recent) refactoring in build script,
This file was over imported iotjs module in TizenRT.

Like done previously with Kconfig file,
it will be better to minimize downstream patches.

One benefit to have those build related files,
is that then IoT.js can be upgraded into TizenRT
by just cloning iotjs's again into subdir:
TizenRT/external/iotjs

Note: Extra minor changes has been done over TizenRT's patch
to make some options overridable from env var (profile file...)

[Sunghan Chang]

Makefile: move IoT.js-specific build step to IoT.js folder

Because Makefile.unix has TizenRT-common build step,
it is not good including IoT.js-specific step.
Let's add Makefile in IoT.js and execute all of step in it.

Thanks-to: sunghan-chang <sh924.chang@samsung.com>
Change-Id: Iddeb272dc6ad6c283ccad9f92bf02754f9ba3240
Bug-TizenRT: Samsung/TizenRT#2111
Origin: Samsung/TizenRT@bbd3cdb
Relate-to: jerryscript-project#1726
Forwarded: jerryscript-project#1732
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
rzr added a commit to TizenTeam/iotjs that referenced this issue Sep 18, 2018
@rzr
tizenrt: Relocate downstream Makefile to config dir (along Kconfig)
07adc76 
[Philippe Coval]

After some (recent) refactoring in build script,
This file was over imported iotjs module in TizenRT.

Like done previously with Kconfig file,
it will be better to minimize downstream patches.

One benefit to have those build related files,
is that then IoT.js can be upgraded into TizenRT
by just cloning iotjs's again into subdir:
TizenRT/external/iotjs

Note: Extra minor changes has been done over TizenRT's patch
to make some options overridable from env var (profile file...)

[Sunghan Chang]

Makefile: move IoT.js-specific build step to IoT.js folder

Because Makefile.unix has TizenRT-common build step,
it is not good including IoT.js-specific step.
Let's add Makefile in IoT.js and execute all of step in it.

Thanks-to: sunghan-chang <sh924.chang@samsung.com>
Change-Id: Iddeb272dc6ad6c283ccad9f92bf02754f9ba3240
Bug-TizenRT: Samsung/TizenRT#2111
Origin: Samsung/TizenRT@bbd3cdb
Relate-to: jerryscript-project#1726
Forwarded: jerryscript-project#1732
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
rzr added a commit to TizenTeam/iotjs that referenced this issue Sep 18, 2018
@rzr
tizenrt: Relocate downstream Makefile to config dir (along Kconfig)
8bdfa24 
[Philippe Coval]

After some (recent) refactoring in build script,
This file was over imported iotjs module in TizenRT.

Like done previously with Kconfig file,
it will be better to minimize downstream patches.

One benefit to have those build related files,
is that then IoT.js can be upgraded into TizenRT
by just cloning iotjs's again into subdir:
TizenRT/external/iotjs

Note: Extra minor changes has been done over TizenRT's patch
to make some options overridable from env var (profile file...)

[Sunghan Chang]

Makefile: move IoT.js-specific build step to IoT.js folder

Because Makefile.unix has TizenRT-common build step,
it is not good including IoT.js-specific step.
Let's add Makefile in IoT.js and execute all of step in it.

Thanks-to: sunghan-chang <sh924.chang@samsung.com>
Change-Id: Iddeb272dc6ad6c283ccad9f92bf02754f9ba3240
Bug-TizenRT: Samsung/TizenRT#2111
Origin: Samsung/TizenRT@bbd3cdb
Relate-to: jerryscript-project#1726
Forwarded: jerryscript-project#1732
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
rzr added a commit to TizenTeam/iotjs that referenced this issue Sep 18, 2018
@rzr
tizenrt: Relocate downstream Makefile to config dir (along Kconfig)
339f8c4 
[Philippe Coval]

After some (recent) refactoring in build script,
This file was over imported iotjs module in TizenRT.

Like done previously with Kconfig file,
it will be better to minimize downstream patches.

One benefit to have those build related files,
is that then IoT.js can be upgraded into TizenRT
by just cloning iotjs's again into subdir:
TizenRT/external/iotjs

Note: Extra minor changes has been done over TizenRT's patch
to make some options overridable from env var (profile file...)

[Sunghan Chang]

Makefile: move IoT.js-specific build step to IoT.js folder

Because Makefile.unix has TizenRT-common build step,
it is not good including IoT.js-specific step.
Let's add Makefile in IoT.js and execute all of step in it.

Thanks-to: sunghan-chang <sh924.chang@samsung.com>
Change-Id: Iddeb272dc6ad6c283ccad9f92bf02754f9ba3240
Bug-TizenRT: Samsung/TizenRT#2111
Origin: Samsung/TizenRT@bbd3cdb
Relate-to: jerryscript-project#1726
Forwarded: jerryscript-project#1732
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
rzr added a commit to TizenTeam/iotjs that referenced this issue Oct 5, 2018
@rzr
tizenrt: Relocate downstream Makefile to config dir (along Kconfig)
62141fc 
[Philippe Coval]

After some (recent) refactoring in build script,
This file was over imported iotjs module in TizenRT.

Like done previously with Kconfig file,
it will be better to minimize downstream patches.

One benefit to have those build related files,
is that then IoT.js can be upgraded into TizenRT
by just cloning iotjs's again into subdir:
TizenRT/external/iotjs

Note: Extra minor changes has been done over TizenRT's patch
to make some options overridable from env var (profile file...)

[Sunghan Chang]

Makefile: move IoT.js-specific build step to IoT.js folder

Because Makefile.unix has TizenRT-common build step,
it is not good including IoT.js-specific step.
Let's add Makefile in IoT.js and execute all of step in it.

Thanks-to: sunghan-chang <sh924.chang@samsung.com>
Change-Id: Iddeb272dc6ad6c283ccad9f92bf02754f9ba3240
Bug-TizenRT: Samsung/TizenRT#2111
Origin: Samsung/TizenRT@bbd3cdb
Relate-to: jerryscript-project#1726
Forwarded: jerryscript-project#1732
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
rzr added a commit to TizenTeam/iotjs that referenced this issue Oct 6, 2018
@rzr
tizenrt: Relocate downstream Makefile to config dir (along Kconfig)
025dbc2 
[Philippe Coval]

After some (recent) refactoring in build script,
This file was over imported iotjs module in TizenRT.

Like done previously with Kconfig file,
it will be better to minimize downstream patches.

One benefit to have those build related files,
is that then IoT.js can be upgraded into TizenRT
by just cloning iotjs's again into subdir:
TizenRT/external/iotjs

Note: Extra minor changes has been done over TizenRT's patch
to make some options overridable from env var (profile file...)

[Sunghan Chang]

Makefile: move IoT.js-specific build step to IoT.js folder

Because Makefile.unix has TizenRT-common build step,
it is not good including IoT.js-specific step.
Let's add Makefile in IoT.js and execute all of step in it.

Thanks-to: sunghan-chang <sh924.chang@samsung.com>
Change-Id: Iddeb272dc6ad6c283ccad9f92bf02754f9ba3240
Bug-TizenRT: Samsung/TizenRT#2111
Origin: Samsung/TizenRT@bbd3cdb
Relate-to: jerryscript-project#1726
Forwarded: jerryscript-project#1732
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
rzr added a commit to TizenTeam/iotjs that referenced this issue Oct 10, 2018
@rzr
tizenrt: Relocate downstream Makefile to config dir (along Kconfig)
dadcb51 
[Philippe Coval]

After some (recent) refactoring in build script,
This file was over imported iotjs module in TizenRT.

Like done previously with Kconfig file,
it will be better to minimize downstream patches.

One benefit to have those build related files,
is that then IoT.js can be upgraded into TizenRT
by just cloning iotjs's again into subdir:
TizenRT/external/iotjs

Note: Extra minor changes has been done over TizenRT's patch
to make some options overridable from env var (profile file...)

[Sunghan Chang]

Makefile: move IoT.js-specific build step to IoT.js folder

Because Makefile.unix has TizenRT-common build step,
it is not good including IoT.js-specific step.
Let's add Makefile in IoT.js and execute all of step in it.

Thanks-to: sunghan-chang <sh924.chang@samsung.com>
Change-Id: Iddeb272dc6ad6c283ccad9f92bf02754f9ba3240
Bug-TizenRT: Samsung/TizenRT#2111
Origin: Samsung/TizenRT@bbd3cdb
Relate-to: jerryscript-project#1726
Forwarded: jerryscript-project#1732
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
rzr added a commit to TizenTeam/iotjs that referenced this issue Oct 18, 2018
@rzr
tizenrt: Relocate downstream Makefile to config dir (along Kconfig)
730a18e 
[Philippe Coval]

After some (recent) refactoring in build script,
This file was over imported iotjs module in TizenRT.

Like done previously with Kconfig file,
it will be better to minimize downstream patches.

One benefit to have those build related files,
is that then IoT.js can be upgraded into TizenRT
by just cloning iotjs's again into subdir:
TizenRT/external/iotjs

Note: Extra minor changes has been done over TizenRT's patch
to make some options overridable from env var (profile file...)

[Sunghan Chang]

Makefile: move IoT.js-specific build step to IoT.js folder

Because Makefile.unix has TizenRT-common build step,
it is not good including IoT.js-specific step.
Let's add Makefile in IoT.js and execute all of step in it.

Thanks-to: sunghan-chang <sh924.chang@samsung.com>
Change-Id: Iddeb272dc6ad6c283ccad9f92bf02754f9ba3240
Bug-TizenRT: Samsung/TizenRT#2111
Origin: Samsung/TizenRT@bbd3cdb
Relate-to: jerryscript-project#1726
Forwarded: jerryscript-project#1732
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
rzr added a commit to TizenTeam/iotjs that referenced this issue Oct 18, 2018
@rzr
tizenrt: Relocate downstream Makefile to config dir (along Kconfig)
c210ea6 
[Philippe Coval]

After some (recent) refactoring in build script,
This file was over imported iotjs module in TizenRT.

Like done previously with Kconfig file,
it will be better to minimize downstream patches.

One benefit to have those build related files,
is that then IoT.js can be upgraded into TizenRT
by just cloning iotjs's again into subdir:
TizenRT/external/iotjs

Note: Extra minor changes has been done over TizenRT's patch
to make some options overridable from env var (profile file...)

[Sunghan Chang]

Makefile: move IoT.js-specific build step to IoT.js folder

Because Makefile.unix has TizenRT-common build step,
it is not good including IoT.js-specific step.
Let's add Makefile in IoT.js and execute all of step in it.

Thanks-to: sunghan-chang <sh924.chang@samsung.com>
Change-Id: Iddeb272dc6ad6c283ccad9f92bf02754f9ba3240
Bug-TizenRT: Samsung/TizenRT#2111
Origin: Samsung/TizenRT@bbd3cdb
Relate-to: jerryscript-project#1726
Forwarded: jerryscript-project#1732
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
rzr added a commit to TizenTeam/iotjs that referenced this issue Oct 22, 2018
@rzr
build: Update TizenRT to 2.0_Public_M2
98bc5a5 
Because current version of TizenRT in IoT.js docker image is oudated,
let's fetch tag from upstream at build time,
to speed up build time, this part can be eventually removed
if image is updated with latest TizenRT's sources.

Use iotjs's defconfig as default config instead of file:
"tizenrt_release_config"
from container:
https://hub.docker.com/r/iotjs/ubuntu/

Is this file tracked anywhere?

Later debug, release configs can tracked in IoT.js's source tree,
and used as desired, for performance benchmarking.

jerryx extra lib has been dropped for now,
this should be reintroduced later (once TizenRT upgrade IoT.js ?)

Bug: jerryscript-project#1777
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com

Disable debuger code if not enabled

Observed build issue on TizenRT (master):

    iotjs.c:58: undefined reference to `jerryx_debugger_tcp_create'
    iotjs.c:59: undefined reference to `jerryx_debugger_ws_create'
    iotjs.c:58: undefined reference to `jerryx_debugger_after_connect'

The whole part is disabled,
even if only jerry-ext functions are not linked (on Tizen:RT master).

Change-Id: Id88c745c9712f6f620bbd200f493397572174ce6
Forwarded: jerryscript-project#1749
Origin: https://github.com/TizenTeam/iotjs/
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval philippe.coval@osg.samsung.com

tizenrt: Update defconfig from TizenRT 2.0

Align to TizenRT default config, but disable SSS for ARTIK053

Bug: jerryscript-project#1777
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com

tizenrt: Relocate downstream Makefile to config dir (along Kconfig)

[Philippe Coval]

After some (recent) refactoring in build script,
This file was over imported iotjs module in TizenRT.

Like done previously with Kconfig file,
it will be better to minimize downstream patches.

One benefit to have those build related files,
is that then IoT.js can be upgraded into TizenRT
by just cloning iotjs's again into subdir:
TizenRT/external/iotjs

Note: Extra minor changes has been done over TizenRT's patch
to make some options overridable from env var (profile file...)

[Sunghan Chang]

Makefile: move IoT.js-specific build step to IoT.js folder

Because Makefile.unix has TizenRT-common build step,
it is not good including IoT.js-specific step.
Let's add Makefile in IoT.js and execute all of step in it.

Thanks-to: sunghan-chang <sh924.chang@samsung.com>
Change-Id: Iddeb272dc6ad6c283ccad9f92bf02754f9ba3240
Bug-TizenRT: Samsung/TizenRT#2111
Origin: Samsung/TizenRT@bbd3cdb
Relate-to: jerryscript-project#1726
Forwarded: jerryscript-project#1732
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
@rzr rzr mentioned this issue Oct 22, 2018
Closed
rzr added a commit to TizenTeam/iotjs that referenced this issue Oct 22, 2018
@rzr
tizenrt: Relocate downstream Makefile to config dir (along Kconfig)
1e15fd0 
[Philippe Coval]

After some (recent) refactoring in build script,
This file was over imported iotjs module in TizenRT.

Like done previously with Kconfig file,
it will be better to minimize downstream patches.

One benefit to have those build related files,
is that then IoT.js can be upgraded into TizenRT
by just cloning iotjs's again into subdir:
TizenRT/external/iotjs

Note: Extra minor changes has been done over TizenRT's patch
to make some options overridable from env var (profile file...)

[Sunghan Chang]

Makefile: move IoT.js-specific build step to IoT.js folder

Because Makefile.unix has TizenRT-common build step,
it is not good including IoT.js-specific step.
Let's add Makefile in IoT.js and execute all of step in it.

Thanks-to: sunghan-chang <sh924.chang@samsung.com>
Change-Id: Iddeb272dc6ad6c283ccad9f92bf02754f9ba3240
Bug-TizenRT: Samsung/TizenRT#2111
Origin: Samsung/TizenRT@bbd3cdb
Relate-to: jerryscript-project#1726
Forwarded: jerryscript-project#1732
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
rzr added a commit to TizenTeam/iotjs that referenced this issue Oct 25, 2018
@rzr
tizenrt: Relocate downstream Makefile to config dir (along Kconfig)
16f7e7e 
[Philippe Coval]

After some (recent) refactoring in build script,
This file was over imported iotjs module in TizenRT.

Like done previously with Kconfig file,
it will be better to minimize downstream patches.

One benefit to have those build related files,
is that then IoT.js can be upgraded into TizenRT
by just cloning iotjs's again into subdir:
TizenRT/external/iotjs

Note: Extra minor changes has been done over TizenRT's patch
to make some options overridable from env var (profile file...)

[Sunghan Chang]

Makefile: move IoT.js-specific build step to IoT.js folder

Because Makefile.unix has TizenRT-common build step,
it is not good including IoT.js-specific step.
Let's add Makefile in IoT.js and execute all of step in it.

Thanks-to: sunghan-chang <sh924.chang@samsung.com>
Change-Id: Iddeb272dc6ad6c283ccad9f92bf02754f9ba3240
Bug-TizenRT: Samsung/TizenRT#2111
Origin: Samsung/TizenRT@bbd3cdb
Relate-to: jerryscript-project#1726
Forwarded: jerryscript-project#1732
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
rzr added a commit to TizenTeam/iotjs that referenced this issue Nov 5, 2018
@rzr
tizenrt: Relocate downstream Makefile to config dir (along Kconfig)
3e5c1ba 
[Philippe Coval]

After some (recent) refactoring in build script,
This file was over imported iotjs module in TizenRT.

Like done previously with Kconfig file,
it will be better to minimize downstream patches.

One benefit to have those build related files,
is that then IoT.js can be upgraded into TizenRT
by just cloning iotjs's again into subdir:
TizenRT/external/iotjs

Note: Extra minor changes has been done over TizenRT's patch
to make some options overridable from env var (profile file...)

[Sunghan Chang]

Makefile: move IoT.js-specific build step to IoT.js folder

Because Makefile.unix has TizenRT-common build step,
it is not good including IoT.js-specific step.
Let's add Makefile in IoT.js and execute all of step in it.

Thanks-to: sunghan-chang <sh924.chang@samsung.com>
Change-Id: Iddeb272dc6ad6c283ccad9f92bf02754f9ba3240
Bug-TizenRT: Samsung/TizenRT#2111
Origin: Samsung/TizenRT@bbd3cdb
Relate-to: jerryscript-project#1726
Forwarded: jerryscript-project#1732
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
rzr added a commit to TizenTeam/iotjs that referenced this issue Nov 5, 2018
@rzr
tizenrt: Relocate downstream Makefile to config dir (along Kconfig)
bee15b7 
[Philippe Coval]

After some (recent) refactoring in build script,
This file was over imported iotjs module in TizenRT.

Like done previously with Kconfig file,
it will be better to minimize downstream patches.

One benefit to have those build related files,
is that then IoT.js can be upgraded into TizenRT
by just cloning iotjs's again into subdir:
TizenRT/external/iotjs

Note: Extra minor changes has been done over TizenRT's patch
to make some options overridable from env var (profile file...)

[Sunghan Chang]

Makefile: move IoT.js-specific build step to IoT.js folder

Because Makefile.unix has TizenRT-common build step,
it is not good including IoT.js-specific step.
Let's add Makefile in IoT.js and execute all of step in it.

Thanks-to: sunghan-chang <sh924.chang@samsung.com>
Change-Id: Iddeb272dc6ad6c283ccad9f92bf02754f9ba3240
Bug-TizenRT: Samsung/TizenRT#2111
Origin: Samsung/TizenRT@bbd3cdb
Relate-to: jerryscript-project#1726
Forwarded: jerryscript-project#1732
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
rzr added a commit to TizenTeam/iotjs that referenced this issue Nov 5, 2018
@rzr
tizenrt: Relocate downstream Makefile to config dir (along Kconfig)
43ab90a 
[Philippe Coval]

After some (recent) refactoring in build script,
This file was over imported iotjs module in TizenRT.

Like done previously with Kconfig file,
it will be better to minimize downstream patches.

One benefit to have those build related files,
is that then IoT.js can be upgraded into TizenRT
by just cloning iotjs's again into subdir:
TizenRT/external/iotjs

Note: Extra minor changes has been done over TizenRT's patch
to make some options overridable from env var (profile file...)

[Sunghan Chang]

Makefile: move IoT.js-specific build step to IoT.js folder

Because Makefile.unix has TizenRT-common build step,
it is not good including IoT.js-specific step.
Let's add Makefile in IoT.js and execute all of step in it.

Thanks-to: sunghan-chang <sh924.chang@samsung.com>
Change-Id: Iddeb272dc6ad6c283ccad9f92bf02754f9ba3240
Bug-TizenRT: Samsung/TizenRT#2111
Origin: Samsung/TizenRT@bbd3cdb
Relate-to: jerryscript-project#1726
Forwarded: jerryscript-project#1732
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
rzr added a commit to TizenTeam/iotjs that referenced this issue Nov 5, 2018
@rzr
tizenrt: Relocate downstream Makefile to config dir (along Kconfig)
a51d5de 
[Philippe Coval]

After some (recent) refactoring in build script,
This file was over imported iotjs module in TizenRT.

Like done previously with Kconfig file,
it will be better to minimize downstream patches.

One benefit to have those build related files,
is that then IoT.js can be upgraded into TizenRT
by just cloning iotjs's again into subdir:
TizenRT/external/iotjs

Note: Extra minor changes has been done over TizenRT's patch
to make some options overridable from env var (profile file...)

[Sunghan Chang]

Makefile: move IoT.js-specific build step to IoT.js folder

Because Makefile.unix has TizenRT-common build step,
it is not good including IoT.js-specific step.
Let's add Makefile in IoT.js and execute all of step in it.

Thanks-to: sunghan-chang <sh924.chang@samsung.com>
Change-Id: Iddeb272dc6ad6c283ccad9f92bf02754f9ba3240
Bug-TizenRT: Samsung/TizenRT#2111
Origin: Samsung/TizenRT@bbd3cdb
Relate-to: jerryscript-project#1726
Forwarded: jerryscript-project#1732
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
rzr added a commit to rzr/iotjs that referenced this issue Nov 8, 2018
@rzr
tizenrt: Relocate downstream Makefile to config dir (along Kconfig)
6f3ab9e 
[Philippe Coval]

After some (recent) refactoring in build script,
This file was over imported iotjs module in TizenRT.

Like done previously with Kconfig file,
it will be better to minimize downstream patches.

One benefit to have those build related files,
is that then IoT.js can be upgraded into TizenRT
by just cloning iotjs's again into subdir:
TizenRT/external/iotjs

Note: Extra minor changes has been done over TizenRT's patch
to make some options overridable from env var (profile file...)

[Sunghan Chang]

Makefile: move IoT.js-specific build step to IoT.js folder

Because Makefile.unix has TizenRT-common build step,
it is not good including IoT.js-specific step.
Let's add Makefile in IoT.js and execute all of step in it.

Thanks-to: sunghan-chang <sh924.chang@samsung.com>
Change-Id: Iddeb272dc6ad6c283ccad9f92bf02754f9ba3240
Bug-TizenRT: Samsung/TizenRT#2111
Origin: Samsung/TizenRT@bbd3cdb
Relate-to: jerryscript-project#1726
Forwarded: jerryscript-project#1732
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
rzr added a commit to TizenTeam/iotjs that referenced this issue Nov 8, 2018
@rzr
tizenrt: Relocate downstream Makefile to config dir (along Kconfig)
25458ff 
[Philippe Coval]

After some (recent) refactoring in build script,
This file was over imported iotjs module in TizenRT.

Like done previously with Kconfig file,
it will be better to minimize downstream patches.

One benefit to have those build related files,
is that then IoT.js can be upgraded into TizenRT
by just cloning iotjs's again into subdir:
TizenRT/external/iotjs

Note: Extra minor changes has been done over TizenRT's patch
to make some options overridable from env var (profile file...)

[Sunghan Chang]

Makefile: move IoT.js-specific build step to IoT.js folder

Because Makefile.unix has TizenRT-common build step,
it is not good including IoT.js-specific step.
Let's add Makefile in IoT.js and execute all of step in it.

Thanks-to: sunghan-chang <sh924.chang@samsung.com>
Change-Id: Iddeb272dc6ad6c283ccad9f92bf02754f9ba3240
Bug-TizenRT: Samsung/TizenRT#2111
Origin: Samsung/TizenRT@bbd3cdb
Relate-to: jerryscript-project#1726
Forwarded: jerryscript-project#1732
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
rzr added a commit to TizenTeam/iotjs that referenced this issue Nov 8, 2018
@rzr
tizenrt: Relocate downstream Makefile to config dir (along Kconfig)
5c1e54d 
[Philippe Coval]

After some (recent) refactoring in build script,
This file was over imported iotjs module in TizenRT.

Like done previously with Kconfig file,
it will be better to minimize downstream patches.

One benefit to have those build related files,
is that then IoT.js can be upgraded into TizenRT
by just cloning iotjs's again into subdir:
TizenRT/external/iotjs

Note: Extra minor changes has been done over TizenRT's patch
to make some options overridable from env var (profile file...)

[Sunghan Chang]

Makefile: move IoT.js-specific build step to IoT.js folder

Because Makefile.unix has TizenRT-common build step,
it is not good including IoT.js-specific step.
Let's add Makefile in IoT.js and execute all of step in it.

Thanks-to: sunghan-chang <sh924.chang@samsung.com>
Change-Id: Iddeb272dc6ad6c283ccad9f92bf02754f9ba3240
Bug-TizenRT: Samsung/TizenRT#2111
Origin: Samsung/TizenRT@bbd3cdb
Relate-to: jerryscript-project#1726
Forwarded: jerryscript-project#1732
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
rzr added a commit to TizenTeam/iotjs that referenced this issue Nov 8, 2018
@rzr
tizenrt: Relocate downstream Makefile to config dir (along Kconfig)
02e817b 
[Philippe Coval]

After some (recent) refactoring in build script,
This file was over imported iotjs module in TizenRT.

Like done previously with Kconfig file,
it will be better to minimize downstream patches.

One benefit to have those build related files,
is that then IoT.js can be upgraded into TizenRT
by just cloning iotjs's again into subdir:
TizenRT/external/iotjs

Note: Extra minor changes has been done over TizenRT's patch
to make some options overridable from env var (profile file...)

[Sunghan Chang]

Makefile: move IoT.js-specific build step to IoT.js folder

Because Makefile.unix has TizenRT-common build step,
it is not good including IoT.js-specific step.
Let's add Makefile in IoT.js and execute all of step in it.

Thanks-to: sunghan-chang <sh924.chang@samsung.com>
Change-Id: Iddeb272dc6ad6c283ccad9f92bf02754f9ba3240
Bug-TizenRT: Samsung/TizenRT#2111
Origin: Samsung/TizenRT@bbd3cdb
Relate-to: jerryscript-project#1726
Forwarded: jerryscript-project#1732
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
rzr added a commit to TizenTeam/iotjs that referenced this issue Nov 9, 2018
@rzr
tizenrt: Relocate downstream Makefile to config dir (along Kconfig)
fe55720 
[Philippe Coval]

After some (recent) refactoring in build script,
This file was over imported iotjs module in TizenRT.

Like done previously with Kconfig file,
it will be better to minimize downstream patches.

One benefit to have those build related files,
is that then IoT.js can be upgraded into TizenRT
by just cloning iotjs's again into subdir:
TizenRT/external/iotjs

Note: Extra minor changes has been done over TizenRT's patch
to make some options overridable from env var (profile file...)

[Sunghan Chang]

Makefile: move IoT.js-specific build step to IoT.js folder

Because Makefile.unix has TizenRT-common build step,
it is not good including IoT.js-specific step.
Let's add Makefile in IoT.js and execute all of step in it.

Thanks-to: sunghan-chang <sh924.chang@samsung.com>
Change-Id: Iddeb272dc6ad6c283ccad9f92bf02754f9ba3240
Bug-TizenRT: Samsung/TizenRT#2111
Origin: Samsung/TizenRT@bbd3cdb
Relate-to: jerryscript-project#1726
Forwarded: jerryscript-project#1732
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
rzr added a commit to TizenTeam/iotjs that referenced this issue Nov 9, 2018
@rzr
tizenrt: Relocate downstream Makefile to config dir (along Kconfig)
efc4780 
[Philippe Coval]

After some (recent) refactoring in build script,
This file was over imported iotjs module in TizenRT.

Like done previously with Kconfig file,
it will be better to minimize downstream patches.

One benefit to have those build related files,
is that then IoT.js can be upgraded into TizenRT
by just cloning iotjs's again into subdir:
TizenRT/external/iotjs

Note: Extra minor changes has been done over TizenRT's patch
to make some options overridable from env var (profile file...)

[Sunghan Chang]

Makefile: move IoT.js-specific build step to IoT.js folder

Because Makefile.unix has TizenRT-common build step,
it is not good including IoT.js-specific step.
Let's add Makefile in IoT.js and execute all of step in it.

Thanks-to: sunghan-chang <sh924.chang@samsung.com>
Change-Id: Iddeb272dc6ad6c283ccad9f92bf02754f9ba3240
Bug-TizenRT: Samsung/TizenRT#2111
Origin: Samsung/TizenRT@bbd3cdb
Relate-to: jerryscript-project#1726
Forwarded: jerryscript-project#1732
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
rzr added a commit to TizenTeam/iotjs that referenced this issue Nov 9, 2018
@rzr
tizenrt: Relocate downstream Makefile to config dir (along Kconfig)
a712247 
[Philippe Coval]

After some (recent) refactoring in build script,
This file was over imported iotjs module in TizenRT.

Like done previously with Kconfig file,
it will be better to minimize downstream patches.

One benefit to have those build related files,
is that then IoT.js can be upgraded into TizenRT
by just cloning iotjs's again into subdir:
TizenRT/external/iotjs

Note: Extra minor changes has been done over TizenRT's patch
to make some options overridable from env var (profile file...)

[Sunghan Chang]

Makefile: move IoT.js-specific build step to IoT.js folder

Because Makefile.unix has TizenRT-common build step,
it is not good including IoT.js-specific step.
Let's add Makefile in IoT.js and execute all of step in it.

Thanks-to: sunghan-chang <sh924.chang@samsung.com>
Change-Id: Iddeb272dc6ad6c283ccad9f92bf02754f9ba3240
Bug-TizenRT: Samsung/TizenRT#2111
Origin: Samsung/TizenRT@bbd3cdb
Relate-to: jerryscript-project#1726
Forwarded: jerryscript-project#1732
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
rzr added a commit to TizenTeam/iotjs that referenced this issue Nov 9, 2018
@rzr
tizenrt: Relocate downstream Makefile to config dir (along Kconfig)
2335628 
[Philippe Coval]

After some (recent) refactoring in build script,
This file was over imported iotjs module in TizenRT.

Like done previously with Kconfig file,
it will be better to minimize downstream patches.

One benefit to have those build related files,
is that then IoT.js can be upgraded into TizenRT
by just cloning iotjs's again into subdir:
TizenRT/external/iotjs

Note: Extra minor changes has been done over TizenRT's patch
to make some options overridable from env var (profile file...)

[Sunghan Chang]

Makefile: move IoT.js-specific build step to IoT.js folder

Because Makefile.unix has TizenRT-common build step,
it is not good including IoT.js-specific step.
Let's add Makefile in IoT.js and execute all of step in it.

Thanks-to: sunghan-chang <sh924.chang@samsung.com>
Change-Id: Iddeb272dc6ad6c283ccad9f92bf02754f9ba3240
Bug-TizenRT: Samsung/TizenRT#2111
Origin: Samsung/TizenRT@bbd3cdb
Relate-to: jerryscript-project#1726
Forwarded: jerryscript-project#1732
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
rzr added a commit to TizenTeam/iotjs that referenced this issue Nov 12, 2018
@rzr
tizenrt: Relocate downstream Makefile to config dir (along Kconfig)
5a26d09 
[Philippe Coval]

After some (recent) refactoring in build script,
This file was over imported iotjs module in TizenRT.

Like done previously with Kconfig file,
it will be better to minimize downstream patches.

One benefit to have those build related files,
is that then IoT.js can be upgraded into TizenRT
by just cloning iotjs's again into subdir:
TizenRT/external/iotjs

Note: Extra minor changes has been done over TizenRT's patch
to make some options overridable from env var (profile file...)

[Sunghan Chang]

Makefile: move IoT.js-specific build step to IoT.js folder

Because Makefile.unix has TizenRT-common build step,
it is not good including IoT.js-specific step.
Let's add Makefile in IoT.js and execute all of step in it.

Thanks-to: sunghan-chang <sh924.chang@samsung.com>
Change-Id: Iddeb272dc6ad6c283ccad9f92bf02754f9ba3240
Bug-TizenRT: Samsung/TizenRT#2111
Origin: Samsung/TizenRT@bbd3cdb
Relate-to: jerryscript-project#1726
Forwarded: jerryscript-project#1732
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
rzr added a commit to TizenTeam/iotjs that referenced this issue Nov 12, 2018
@rzr
tizenrt: Relocate downstream Makefile to config dir (along Kconfig)
4f8f687 
[Philippe Coval]

After some (recent) refactoring in build script,
This file was over imported iotjs module in TizenRT.

Like done previously with Kconfig file,
it will be better to minimize downstream patches.

One benefit to have those build related files,
is that then IoT.js can be upgraded into TizenRT
by just cloning iotjs's again into subdir:
TizenRT/external/iotjs

Note: Extra minor changes has been done over TizenRT's patch
to make some options overridable from env var (profile file...)

[Sunghan Chang]

Makefile: move IoT.js-specific build step to IoT.js folder

Because Makefile.unix has TizenRT-common build step,
it is not good including IoT.js-specific step.
Let's add Makefile in IoT.js and execute all of step in it.

Thanks-to: sunghan-chang <sh924.chang@samsung.com>
Change-Id: Iddeb272dc6ad6c283ccad9f92bf02754f9ba3240
Bug-TizenRT: Samsung/TizenRT#2111
Origin: Samsung/TizenRT@bbd3cdb
Relate-to: jerryscript-project#1726
Forwarded: jerryscript-project#1732
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
rzr added a commit to TizenTeam/iotjs that referenced this issue Nov 13, 2018
@rzr
tizenrt: Relocate downstream Makefile to config dir (along Kconfig)
3b8162e 
[Philippe Coval]

After some (recent) refactoring in build script,
This file was over imported iotjs module in TizenRT.

Like done previously with Kconfig file,
it will be better to minimize downstream patches.

One benefit to have those build related files,
is that then IoT.js can be upgraded into TizenRT
by just cloning iotjs's again into subdir:
TizenRT/external/iotjs

Note: Extra minor changes has been done over TizenRT's patch
to make some options overridable from env var (profile file...)

[Sunghan Chang]

Makefile: move IoT.js-specific build step to IoT.js folder

Because Makefile.unix has TizenRT-common build step,
it is not good including IoT.js-specific step.
Let's add Makefile in IoT.js and execute all of step in it.

Thanks-to: sunghan-chang <sh924.chang@samsung.com>
Change-Id: Iddeb272dc6ad6c283ccad9f92bf02754f9ba3240
Bug-TizenRT: Samsung/TizenRT#2111
Origin: Samsung/TizenRT@bbd3cdb
Relate-to: jerryscript-project#1726
Forwarded: jerryscript-project#1732
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
rzr added a commit to TizenTeam/iotjs that referenced this issue Nov 15, 2018
@rzr
tizenrt: Relocate downstream Makefile to config dir (along Kconfig)
7cd0afc 
[Philippe Coval]

After some (recent) refactoring in build script,
This file was over imported iotjs module in TizenRT.

Like done previously with Kconfig file,
it will be better to minimize downstream patches.

One benefit to have those build related files,
is that then IoT.js can be upgraded into TizenRT
by just cloning iotjs's again into subdir:
TizenRT/external/iotjs

Note: Extra minor changes has been done over TizenRT's patch
to make some options overridable from env var (profile file...)

[Sunghan Chang]

Makefile: move IoT.js-specific build step to IoT.js folder

Because Makefile.unix has TizenRT-common build step,
it is not good including IoT.js-specific step.
Let's add Makefile in IoT.js and execute all of step in it.

Thanks-to: sunghan-chang <sh924.chang@samsung.com>
Change-Id: Iddeb272dc6ad6c283ccad9f92bf02754f9ba3240
Bug-TizenRT: Samsung/TizenRT#2111
Origin: Samsung/TizenRT@bbd3cdb
Relate-to: jerryscript-project#1726
Forwarded: jerryscript-project#1732
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
rzr added a commit to TizenTeam/iotjs that referenced this issue Nov 27, 2018
@rzr
tizenrt: Relocate downstream Makefile to config dir (along Kconfig)
ba1489f 
[Philippe Coval]

After some (recent) refactoring in build script,
This file was over imported iotjs module in TizenRT.

Like done previously with Kconfig file,
it will be better to minimize downstream patches.

One benefit to have those build related files,
is that then IoT.js can be upgraded into TizenRT
by just cloning iotjs's again into subdir:
TizenRT/external/iotjs

Note: Extra minor changes has been done over TizenRT's patch
to make some options overridable from env var (profile file...)

[Sunghan Chang]

Makefile: move IoT.js-specific build step to IoT.js folder

Because Makefile.unix has TizenRT-common build step,
it is not good including IoT.js-specific step.
Let's add Makefile in IoT.js and execute all of step in it.

Thanks-to: sunghan-chang <sh924.chang@samsung.com>
Change-Id: Iddeb272dc6ad6c283ccad9f92bf02754f9ba3240
Bug-TizenRT: Samsung/TizenRT#2111
Origin: Samsung/TizenRT@bbd3cdb
Relate-to: jerryscript-project#1726
Forwarded: jerryscript-project#1732
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
@rzr rzr mentioned this issue Nov 27, 2018
Merged
rzr added a commit to TizenTeam/iotjs that referenced this issue Nov 27, 2018
@rzr
tizenrt: Relocate downstream Makefile to config dir (along Kconfig)
8cd449c 
[Philippe Coval]

After some (recent) refactoring in build script,
This file was over imported iotjs module in TizenRT.

Like done previously with Kconfig file,
it will be better to minimize downstream patches.

One benefit to have those build related files,
is that then IoT.js can be upgraded into TizenRT
by just cloning iotjs's again into subdir:
TizenRT/external/iotjs

Note: Extra minor changes has been done over TizenRT's patch
to make some options overridable from env var (profile file...)

[Sunghan Chang]

Makefile: move IoT.js-specific build step to IoT.js folder

Because Makefile.unix has TizenRT-common build step,
it is not good including IoT.js-specific step.
Let's add Makefile in IoT.js and execute all of step in it.

Thanks-to: sunghan-chang <sh924.chang@samsung.com>
Change-Id: Iddeb272dc6ad6c283ccad9f92bf02754f9ba3240
Bug: jerryscript-project#1777
Bug-TizenRT: Samsung/TizenRT#2111
Origin: Samsung/TizenRT@bbd3cdb
Relate-to: jerryscript-project#1726
Forwarded: jerryscript-project#1809
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
rzr added a commit to TizenTeam/iotjs that referenced this issue Nov 27, 2018
@rzr
tizenrt: Relocate downstream Makefile to config dir (along Kconfig)
f51b6e1 
[Philippe Coval]

After some (recent) refactoring in build script,
This file was over imported iotjs module in TizenRT.

Like done previously with Kconfig file,
it will be better to minimize downstream patches.

One benefit to have those build related files,
is that then IoT.js can be upgraded into TizenRT
by just cloning iotjs's again into subdir:
TizenRT/external/iotjs

Note: Extra minor changes has been done over TizenRT's patch
to make some options overridable from env var (profile file...)

[Sunghan Chang]

Makefile: move IoT.js-specific build step to IoT.js folder

Because Makefile.unix has TizenRT-common build step,
it is not good including IoT.js-specific step.
Let's add Makefile in IoT.js and execute all of step in it.

Thanks-to: sunghan-chang <sh924.chang@samsung.com>
Change-Id: Iddeb272dc6ad6c283ccad9f92bf02754f9ba3240
Bug: jerryscript-project#1777
Bug-TizenRT: Samsung/TizenRT#2111
Origin: Samsung/TizenRT@bbd3cdb
Relate-to: jerryscript-project#1726
Forwarded: jerryscript-project#1809
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
rzr added a commit to TizenTeam/iotjs that referenced this issue Nov 27, 2018
@rzr
tizenrt: Relocate downstream Makefile to config dir (along Kconfig)
e5b84ff 
[Philippe Coval]

After some (recent) refactoring in build script,
This file was over imported iotjs module in TizenRT.

Like done previously with Kconfig file,
it will be better to minimize downstream patches.

One benefit to have those build related files,
is that then IoT.js can be upgraded into TizenRT
by just cloning iotjs's again into subdir:
TizenRT/external/iotjs

Note: Extra minor changes has been done over TizenRT's patch:

- make some options overridable from env var (profile file...)
- add smooth transition to use sys/uio.h introduced after TizenRT 2

[Sunghan Chang]

Makefile: move IoT.js-specific build step to IoT.js folder

Because Makefile.unix has TizenRT-common build step,
it is not good including IoT.js-specific step.
Let's add Makefile in IoT.js and execute all of step in it.

Thanks-to: sunghan-chang <sh924.chang@samsung.com>
Change-Id: Iddeb272dc6ad6c283ccad9f92bf02754f9ba3240
Bug: jerryscript-project#1777
Bug-TizenRT: Samsung/TizenRT#2111
Origin: Samsung/TizenRT@bbd3cdb
Relate-to: jerryscript-project#1726
Forwarded: jerryscript-project#1809
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
rzr added a commit to TizenTeam/iotjs that referenced this issue Nov 28, 2018
@rzr
tizenrt: Relocate downstream Makefile to config dir (along Kconfig)
c4bfd37 
[Philippe Coval]

After some (recent) refactoring in build script,
This file was over imported iotjs module in TizenRT.

Like done previously with Kconfig file,
it will be better to minimize downstream patches.

One benefit to have those build related files,
is that then IoT.js can be upgraded into TizenRT
by just cloning iotjs's again into subdir:
TizenRT/external/iotjs

Note: Extra minor changes has been done over TizenRT's patch:

- make some options overridable from env var (profile file...)
- add smooth transition to use sys/uio.h introduced after TizenRT 2

[Sunghan Chang]

Makefile: move IoT.js-specific build step to IoT.js folder

Because Makefile.unix has TizenRT-common build step,
it is not good including IoT.js-specific step.
Let's add Makefile in IoT.js and execute all of step in it.

Thanks-to: sunghan-chang <sh924.chang@samsung.com>
Change-Id: Iddeb272dc6ad6c283ccad9f92bf02754f9ba3240
Bug: jerryscript-project#1777
Bug-TizenRT: Samsung/TizenRT#2111
Origin: Samsung/TizenRT@bbd3cdb
Relate-to: jerryscript-project#1726
Forwarded: jerryscript-project#1809
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
rzr added a commit to TizenTeam/iotjs that referenced this issue Nov 28, 2018
@rzr
tizenrt: Relocate downstream Makefile to config dir (along Kconfig)
cc60b40 
[Philippe Coval]

After some (recent) refactoring in build script,
This file was over imported iotjs module in TizenRT.

Like done previously with Kconfig file,
it will be better to minimize downstream patches.

One benefit to have those build related files,
is that then IoT.js can be upgraded into TizenRT
by just cloning iotjs's again into subdir:
TizenRT/external/iotjs

Note: Extra minor changes has been done over TizenRT's patch:

- make some options overridable from env var (profile file...)
- add smooth transition to use sys/uio.h introduced after TizenRT 2

[Sunghan Chang]

Makefile: move IoT.js-specific build step to IoT.js folder

Because Makefile.unix has TizenRT-common build step,
it is not good including IoT.js-specific step.
Let's add Makefile in IoT.js and execute all of step in it.

Thanks-to: sunghan-chang <sh924.chang@samsung.com>
Change-Id: Iddeb272dc6ad6c283ccad9f92bf02754f9ba3240
Bug: jerryscript-project#1777
Bug-TizenRT: Samsung/TizenRT#2111
Origin: Samsung/TizenRT@bbd3cdb
Relate-to: jerryscript-project#1726
Forwarded: jerryscript-project#1809
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
rzr added a commit to TizenTeam/iotjs that referenced this issue Nov 28, 2018
@rzr
tizenrt: Relocate downstream Makefile to config dir (along Kconfig)
dd39be7 
[Philippe Coval]

After some (recent) refactoring in build script,
This file was over imported iotjs module in TizenRT.

Like done previously with Kconfig file,
it will be better to minimize downstream patches.

One benefit to have those build related files,
is that then IoT.js can be upgraded into TizenRT
by just cloning iotjs's again into subdir:
TizenRT/external/iotjs

Note: Extra minor changes has been done over TizenRT's patch:

- make some options overridable from env var (profile file...)
- add smooth transition to use sys/uio.h introduced after TizenRT 2

[Sunghan Chang]

Makefile: move IoT.js-specific build step to IoT.js folder

Because Makefile.unix has TizenRT-common build step,
it is not good including IoT.js-specific step.
Let's add Makefile in IoT.js and execute all of step in it.

Thanks-to: sunghan-chang <sh924.chang@samsung.com>
Change-Id: Iddeb272dc6ad6c283ccad9f92bf02754f9ba3240
Bug: jerryscript-project#1777
Bug-TizenRT: Samsung/TizenRT#2111
Origin: Samsung/TizenRT@bbd3cdb
Relate-to: jerryscript-project#1726
Forwarded: jerryscript-project#1809
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
rzr added a commit to TizenTeam/iotjs that referenced this issue Dec 7, 2018
@rzr
tizenrt: Relocate downstream Makefile to config dir (along Kconfig)
29edac5 
[Philippe Coval]

After some (recent) refactoring in build script,
This file was over imported iotjs module in TizenRT.

Like done previously with Kconfig file,
it will be better to minimize downstream patches.

One benefit to have those build related files,
is that then IoT.js can be upgraded into TizenRT
by just cloning iotjs's again into subdir:
TizenRT/external/iotjs

Note: Extra minor changes has been done over TizenRT's patch:

- make some options overridable from env var (profile file...)
- add smooth transition to use sys/uio.h introduced after TizenRT 2

[Sunghan Chang]

Makefile: move IoT.js-specific build step to IoT.js folder

Because Makefile.unix has TizenRT-common build step,
it is not good including IoT.js-specific step.
Let's add Makefile in IoT.js and execute all of step in it.

Thanks-to: sunghan-chang <sh924.chang@samsung.com>
Change-Id: Iddeb272dc6ad6c283ccad9f92bf02754f9ba3240
Bug: jerryscript-project#1777
Bug-TizenRT: Samsung/TizenRT#2111
Origin: Samsung/TizenRT@bbd3cdb
Relate-to: jerryscript-project#1726
Forwarded: jerryscript-project#1809
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
yichoi pushed a commit that referenced this issue Dec 11, 2018
@rzr @yichoi
tizenrt: Relocate downstream Makefile to config dir (along Kconfig) (#…
5f3693b 
…1809)

[Philippe Coval]

After some (recent) refactoring in build script,
This file was over imported iotjs module in TizenRT.

Like done previously with Kconfig file,
it will be better to minimize downstream patches.

One benefit to have those build related files,
is that then IoT.js can be upgraded into TizenRT
by just cloning iotjs's again into subdir:
TizenRT/external/iotjs

Note: Extra minor changes has been done over TizenRT's patch:

- make some options overridable from env var (profile file...)
- add smooth transition to use sys/uio.h introduced after TizenRT 2

[Sunghan Chang]

Makefile: move IoT.js-specific build step to IoT.js folder

Because Makefile.unix has TizenRT-common build step,
it is not good including IoT.js-specific step.
Let's add Makefile in IoT.js and execute all of step in it.

Thanks-to: sunghan-chang <sh924.chang@samsung.com>
Change-Id: Iddeb272dc6ad6c283ccad9f92bf02754f9ba3240
Bug: #1777
Bug-TizenRT: Samsung/TizenRT#2111
Origin: Samsung/TizenRT@bbd3cdb
Relate-to: #1726
Forwarded: #1809
IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@rzr @daeyeon @LaszloLango