Hi!
Is there a Non-Commercial version of 6.3 available just like there’s the
6.2.1 NC?
Cheers,
allu
Aleksanteri Aaltonen <allu@lumisade.com> wrote:
AA > Hi!
AA > Is there a Non-Commercial version of 6.3 available just like there’s the
AA > 6.2.1 NC?
AA > Cheers,
AA > allu
Kind of.
You can download the evaluation version. It will work like PE for 30
days. After 30 days if you haven’t bought the license, it reverts to a
NC version.
Hello,
You can download the evaluation version. It will work like PE for 30
days. After 30 days if you haven’t bought the license, it reverts to a
NC version.
But what happens when it turns to NC? Can you use it as 6.2.1 NC or there
are some limitations?
Darius
Darius wrote:
Hello,
You can download the evaluation version. It will work like PE for 30
days. After 30 days if you haven’t bought the license, it reverts to a
NC version.
But what happens when it turns to NC? Can you use it as 6.2.1 NC or there
are some limitations?
It’s a bit different to 6.2NC. All it’s development features are pretty
much disabled while the license is expired.
The simple answer is to fiddle with code with the date set wrong. It’s
quite easy to re-enable the license while the date is set before the 30
day limit. Fiddling the date is a small price to pay imho.
Another option is to have more than one box, one for coding and the
other for managing file dates and other activities like posting the
finished results online.
But what happens when it turns to NC? Can you use it as 6.2.1 NC or there
are some limitations?
Only different between 6.2.1NC and 6.3.0NC is that qcc is disabled with
6.3.0NC, but gcc still works.
chris
–
Chris McKillop <cdm@qnx.com> “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/
Chris McKillop wrote:
But what happens when it turns to NC? Can you use it as 6.2.1 NC or there
are some limitations?
Only different between 6.2.1NC and 6.3.0NC is that qcc is disabled with
6.3.0NC, but gcc still works.chris
All qcc does is rearrange the options and call gcc, right?
What’s the point?
A generally useable desktop NC version is a big win for QSSL.
Where is a pool of developers going to come from if there’s
no easily available version of the product? Quit worrying about
somebody stealing the thing. Worry about people ignoring it.
Which is what actually happens in the real world.
John Nagle
Team Overbot
John Nagle <nagle@downside.com> wrote:
All qcc does is rearrange the options and call gcc, right?
QSS, please put qcc back to NC.
It seems somethings gcc just not working unless you use qcc.
I am sure if you tweak gcc options here and there, it will work,
but why not just put qcc back to NC?
http://www.openqnx.com/modules.php?op=modload&name=NewsPortal&file=article&id=953&group=qnx.rtos
is one example.
Frank
What’s the point?
A generally useable desktop NC version is a big win for QSSL.
Where is a pool of developers going to come from if there’s
no easily available version of the product? Quit worrying about
somebody stealing the thing. Worry about people ignoring it.
Which is what actually happens in the real world.John Nagle
Team Overbot