Menu
▾
▴
nsis-devel
|
From: Wizou <sou...@wi...> - 2010-06-16 12:43:12
|
I must also do these things for Unicode NSIS :
* Update documentation
* Convert NLF & NSH language files to Unicode
* Make sure NSIS works fine with pure-Unicode languages (that have
no associated codepages)
* Import pure-Unicode language files that were added to Jim Park's
repository
That is easy to do, but the thing is :
I cannot complete these tasks until you give me green light about not
using ANSI MakeNsis.exe anymore.
(because ANSI version cannot support Unicode NLF)
So please test & review the latest Unicode version and tell me when I
can proceed
|
|
From: Wizou <sou...@wi...> - 2010-06-24 23:40:35
|
I would appreciate to get an answer quickly, before I go in holidays and completely forget all the development I've done so far and it would take me a lot more time to get back into it and make things correctly... I feel that having a Unicode-compatible NSIS is very important for all the people using NSIS, so please don't wait too much in this subject.. especially as I'm ready to finish all the hard work.. I'm very confident in all the changes I've submitted already, so i just need your green light on the fact we won't be using the ANSI build of makensis.exe anymore.. (You just need to check that Unicode NSIS gives good results on various installers scripts, either generating ANSI or Unicode installers) Then I will be able to complete these last steps I explained below Wizou a écrit : > I must also do these things for Unicode NSIS : > > * Update documentation > * Convert NLF & NSH language files to Unicode > * Make sure NSIS works fine with pure-Unicode languages (that have > no associated codepages) > * Import pure-Unicode language files that were added to Jim Park's > repository > > That is easy to do, but the thing is : > I cannot complete these tasks until you give me green light about not > using ANSI MakeNsis.exe anymore. > (because ANSI version cannot support Unicode NLF) > > So please test & review the latest Unicode version and tell me when I > can proceed > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo > ------------------------------------------------------------------------ > > _______________________________________________ > Nsis-devel mailing list > Nsi...@li... > https://lists.sourceforge.net/lists/listinfo/nsis-devel > |
|
From: Amir S. <ki...@gm...> - 2010-06-27 09:04:47
|
I'm good with dropping ANSI makensis.exe. Most sane developers will be running Windows XP and above anyway. Backward compatibility, as important as it is, has its limits too... On Fri, Jun 25, 2010 at 2:40 AM, Wizou <sou...@wi...> wrote: > I would appreciate to get an answer quickly, before I go in holidays and > completely forget all the development I've done so far and it would take me > a lot more time to get back into it and make things correctly... > I feel that having a Unicode-compatible NSIS is very important for all the > people using NSIS, so please don't wait too much in this subject.. > especially as I'm ready to finish all the hard work.. > I'm very confident in all the changes I've submitted already, so i just > need your green light on the fact we won't be using the ANSI build of > makensis.exe anymore.. > (You just need to check that Unicode NSIS gives good results on various > installers scripts, either generating ANSI or Unicode installers) > Then I will be able to complete these last steps I explained below > > > Wizou a écrit : > > I must also do these things for Unicode NSIS : > > - Update documentation > - Convert NLF & NSH language files to Unicode > - Make sure NSIS works fine with pure-Unicode languages (that have no > associated codepages) > - Import pure-Unicode language files that were added to Jim Park's > repository > > That is easy to do, but the thing is : > I cannot complete these tasks until you give me green light about not using > ANSI MakeNsis.exe anymore. > (because ANSI version cannot support Unicode NLF) > > So please test & review the latest Unicode version and tell me when I can > proceed > > ------------------------------ > > ------------------------------------------------------------------------------ > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo > > ------------------------------ > > _______________________________________________ > Nsis-devel mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/nsis-devel > > > > ------------------------------------------------------------------------------ > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo > _______________________________________________ > Nsis-devel mailing list > Nsi...@li... > https://lists.sourceforge.net/lists/listinfo/nsis-devel > > |
|
From: Anders <and...@us...> - 2010-07-02 02:48:36
|
Maybe we should do one final ANSI release? The last release was in 2009, I'm sure useful things have been committed since then (I was actually under the impression that we would ship both versions side by side for a while, why else did we move to TCHAR and not just WCHAR?) Also, IIRC you can't build the unicode version with VC6 because of template problems with the code that has been added |
|
From: Wizou <sou...@wi...> - 2010-07-03 16:56:13
|
Can you tell me how to compile with VC6 ? Again I have spent 1 hour trying a lot of different ways to have Scons use my VC6 correctly and it doesn't work because I have multiple versions of Visual Studio installed.. It either compile with the wrong compiler, or it uses the good compiler with the wrong parameters I'm sorry to say this, but to me Scons looks like a piece of sh** ... It seems to bring much more trouble than the help it provides in setting up a build system One developer shouldn't have to spend so much time on the build system itself ! I'm exasperated Anders a écrit : > Maybe we should do one final ANSI release? The last release was in > 2009, I'm sure useful things have been committed since then (I was > actually under the impression that we would ship both versions side by > side for a while, why else did we move to TCHAR and not just WCHAR?) > > Also, IIRC you can't build the unicode version with VC6 because of > template problems with the code that has been added > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > ------------------------------------------------------------------------ > > _______________________________________________ > Nsis-devel mailing list > Nsi...@li... > https://lists.sourceforge.net/lists/listinfo/nsis-devel > |
|
From: Anders <and...@us...> - 2010-07-03 19:12:58
|
Yeah, I'm not a scons fan either. My exact setup is scons 1.2, VC6 SP5+Processor Pack and Platform SDK Feb. 2003 I just run the "Set Windows XP 32-bit Build Environment (Retail)" shortcut and type the scons command in that window (But I only have one VS version on this system, you might have to run VC6's VCVARS32.BAT in the build terminal or something like that to select the correct compiler) |
|
From: Amir S. <ki...@gm...> - 2010-07-03 22:59:16
|
What exactly are we talking about here? All I get with VC6 is errors about invalid casting. What does SCons has to do with this? On Sat, Jul 3, 2010 at 10:12 PM, Anders <and...@us...>wrote: > Yeah, I'm not a scons fan either. > > My exact setup is scons 1.2, VC6 SP5+Processor Pack and Platform SDK Feb. > 2003 > > I just run the "Set Windows XP 32-bit Build Environment (Retail)" shortcut > and type the scons command in that window (But I only have one VS version on > this system, you might have to run VC6's VCVARS32.BAT in the build terminal > or something like that to select the correct compiler) > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > _______________________________________________ > Nsis-devel mailing list > Nsi...@li... > https://lists.sourceforge.net/lists/listinfo/nsis-devel > > |
|
From: Wizou <sou...@wi...> - 2010-07-04 00:23:00
|
I was finally able to make scons compile with my VC6 (I commited an option MSVS_VERSION to SConstruct) Anders was talking about VC6 with the option UNICODE=yes. It fails on GenPath Checksums.cpp After investigation, what I found is that the C++ Standard library that comes with VC6 has no possibility to open fstream files using Unicode pathnames. It's not a matter of template (the "char" in the template is the kind of objects to read from the files, not the pathname kind) There is not much we can do in this case. So my opinion is that we shouldn't support VC6 compilation anymore As more recent Visual Studio compilers are available for free, I think it's not a bad choice. Amir Szekely a écrit : > What exactly are we talking about here? All I get with VC6 is errors > about invalid casting. > What does SCons has to do with this? > > On Sat, Jul 3, 2010 at 10:12 PM, Anders > <and...@us... > <mailto:and...@us...>> wrote: > > Yeah, I'm not a scons fan either. > > My exact setup is scons 1.2, VC6 SP5+Processor Pack and Platform > SDK Feb. 2003 > > I just run the "Set Windows XP 32-bit Build Environment (Retail)" > shortcut and type the scons command in that window (But I only > have one VS version on this system, you might have to run VC6's > VCVARS32.BAT in the build terminal or something like that to > select the correct compiler) > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first <http://sprint.com/first> -- > http://p.sf.net/sfu/sprint-com-first > _______________________________________________ > Nsis-devel mailing list > Nsi...@li... > <mailto:Nsi...@li...> > https://lists.sourceforge.net/lists/listinfo/nsis-devel > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > ------------------------------------------------------------------------ > > _______________________________________________ > Nsis-devel mailing list > Nsi...@li... > https://lists.sourceforge.net/lists/listinfo/nsis-devel > |
|
From: Wizou <sou...@wi...> - 2010-07-04 00:29:54
|
mmh basic_fstream::open() with wchar_t* appeared with VC8 VC7 does not support Unicode pathname also.. Wizou a écrit : > I was finally able to make scons compile with my VC6 (I commited an > option MSVS_VERSION to SConstruct) > > Anders was talking about VC6 with the option UNICODE=yes. It fails on > GenPath Checksums.cpp > After investigation, what I found is that the C++ Standard library > that comes with VC6 has no possibility to open fstream files using > Unicode pathnames. > It's not a matter of template (the "char" in the template is the kind > of objects to read from the files, not the pathname kind) > > There is not much we can do in this case. > So my opinion is that we shouldn't support VC6 compilation anymore > As more recent Visual Studio compilers are available for free, I think > it's not a bad choice. > > > Amir Szekely a écrit : >> What exactly are we talking about here? All I get with VC6 is errors >> about invalid casting. >> What does SCons has to do with this? >> >> On Sat, Jul 3, 2010 at 10:12 PM, Anders >> <and...@us... >> <mailto:and...@us...>> wrote: >> >> Yeah, I'm not a scons fan either. >> >> My exact setup is scons 1.2, VC6 SP5+Processor Pack and Platform >> SDK Feb. 2003 >> >> I just run the "Set Windows XP 32-bit Build Environment (Retail)" >> shortcut and type the scons command in that window (But I only >> have one VS version on this system, you might have to run VC6's >> VCVARS32.BAT in the build terminal or something like that to >> select the correct compiler) >> >> ------------------------------------------------------------------------------ >> This SF.net email is sponsored by Sprint >> What will you do first with EVO, the first 4G phone? >> Visit sprint.com/first <http://sprint.com/first> -- >> http://p.sf.net/sfu/sprint-com-first >> _______________________________________________ >> Nsis-devel mailing list >> Nsi...@li... >> <mailto:Nsi...@li...> >> https://lists.sourceforge.net/lists/listinfo/nsis-devel >> >> >> ------------------------------------------------------------------------ >> >> ------------------------------------------------------------------------------ >> This SF.net email is sponsored by Sprint >> What will you do first with EVO, the first 4G phone? >> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Nsis-devel mailing list >> Nsi...@li... >> https://lists.sourceforge.net/lists/listinfo/nsis-devel >> > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > ------------------------------------------------------------------------ > > _______________________________________________ > Nsis-devel mailing list > Nsi...@li... > https://lists.sourceforge.net/lists/listinfo/nsis-devel > |
|
From: Anders <and...@us...> - 2010-07-04 13:49:19
|
It must be possible to work around this somehow so we can still use VC6. If we move to VC8 support we will lose NT4 support, if we go all the way to VC10, we lose 2000 support. |
|
From: Wizou <sou...@wi...> - 2010-07-04 15:12:18
|
i will search a work-around. do you have (official?) sources about VC8 not supporting NT4? Anders a écrit : > It must be possible to work around this somehow so we can still use > VC6. If we move to VC8 support we will lose NT4 support, if we go all > the way to VC10, we lose 2000 support. > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > ------------------------------------------------------------------------ > > _______________________________________________ > Nsis-devel mailing list > Nsi...@li... > https://lists.sourceforge.net/lists/listinfo/nsis-devel > |
|
From: Anders <and...@us...> - 2010-07-04 16:12:26
|
No, I don't have a official link, but http://www.legacyextender.com/ would not exist if it was not true. (VC sets the Subsystem value in the PE header to 5.0 etc) |
|
From: Wizou <sou...@wi...> - 2010-07-02 13:01:15
|
It might be a good idea to make a final ANSI release.. or at least to create a SVN branch for ANSI maintenance, just in case Unicode version takes some time to become stable (you never know) I will take a look at the VC6/template issue (if I can actually remember how to make Scons use VC6 correctly) PS: kichik, can you change the mailing-list config so that default answer to mails goes to the mailing-list address instead of the author's address ? Anders a écrit : > Maybe we should do one final ANSI release? The last release was in > 2009, I'm sure useful things have been committed since then (I was > actually under the impression that we would ship both versions side by > side for a while, why else did we move to TCHAR and not just WCHAR?) > > Also, IIRC you can't build the unicode version with VC6 because of > template problems with the code that has been added > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > ------------------------------------------------------------------------ > > _______________________________________________ > Nsis-devel mailing list > Nsi...@li... > https://lists.sourceforge.net/lists/listinfo/nsis-devel > |
|
From: Amir S. <ki...@gm...> - 2010-07-03 10:41:40
|
TCHARs are there so we can create both ANSI and Unicode installers. I rather get started with betas of the Unicode makensis version instead of another ANSI release. On Fri, Jul 2, 2010 at 3:14 PM, Wizou <sou...@wi...> wrote: > It might be a good idea to make a final ANSI release.. > or at least to create a SVN branch for ANSI maintenance, just in case > Unicode version takes some time to become stable (you never know) > > I will take a look at the VC6/template issue (if I can actually remember > how to make Scons use VC6 correctly) > > > PS: kichik, can you change the mailing-list config so that default answer > to mails goes to the mailing-list address instead of the author's address ? > > > Anders a écrit : > > Maybe we should do one final ANSI release? The last release was in 2009, > I'm sure useful things have been committed since then (I was actually under > the impression that we would ship both versions side by side for a while, > why else did we move to TCHAR and not just WCHAR?) > > Also, IIRC you can't build the unicode version with VC6 because of template > problems with the code that has been added > > ------------------------------ > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > > ------------------------------ > > _______________________________________________ > Nsis-devel mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/nsis-devel > > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > _______________________________________________ > Nsis-devel mailing list > Nsi...@li... > https://lists.sourceforge.net/lists/listinfo/nsis-devel > > |
|
From: Anders <and...@us...> - 2010-07-03 14:50:08
|
I'm working on a fix for the locallow issue, we really need to push out a ansi release with that in it (The ansi part of it works, I have not been able to compile the unicode version and I'm not sure how smart it is to commit untested stuff (only a cople lines of code, but still)) |
|
From: Wizou <sou...@wi...> - 2010-07-04 18:55:54
|
bad news VC6 & VC7 runtime library don't support _O_U8TEXT , _O_U16TEXT , ccs=UTF-8 , ccs=UTF-16LE i.e. no support for the various encoding of Unicode (except maybe plain UCS2) so really we cannot stay with these compilers... Note: /SUBSYSTEM:WINDOWS,major,minor can be used to change specific OS requirement I don't know if there are other problems regarding VC8 & NT4.. maybe we can work around these (but I don't have NT4 to test) Personnally, I don't think many NSIS scripters will be building on NT4.. Wizou a écrit : > i will search a work-around. > do you have (official?) sources about VC8 not supporting NT4? > > > > Anders a écrit : >> It must be possible to work around this somehow so we can still use >> VC6. If we move to VC8 support we will lose NT4 support, if we go all >> the way to VC10, we lose 2000 support. >> ------------------------------------------------------------------------ >> >> ------------------------------------------------------------------------------ >> This SF.net email is sponsored by Sprint >> What will you do first with EVO, the first 4G phone? >> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Nsis-devel mailing list >> Nsi...@li... >> https://lists.sourceforge.net/lists/listinfo/nsis-devel >> > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > ------------------------------------------------------------------------ > > _______________________________________________ > Nsis-devel mailing list > Nsi...@li... > https://lists.sourceforge.net/lists/listinfo/nsis-devel > |
|
From: Wizou <sou...@wi...> - 2010-07-08 18:45:50
|
good luck... support of file streams with ANSI / UTF8 / UTF16 format is deep inside the C runtime library... Anders a écrit : > I want to try to keep the vc6 support, even if that means we need some > custom STL templates or change some code, I believe Kichik feels the > same way... > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > ------------------------------------------------------------------------ > > _______________________________________________ > Nsis-devel mailing list > Nsi...@li... > https://lists.sourceforge.net/lists/listinfo/nsis-devel > |
|
From: Anders <and...@us...> - 2010-07-08 14:49:33
|
I want to try to keep the vc6 support, even if that means we need some custom STL templates or change some code, I believe Kichik feels the same way... |
|
From: Anders <and...@us...> - 2010-07-08 22:20:21
|
Well, I have compiled the unicode version in the past on vc6 (The Jim Park fork IIRC, possibly from main svn early in the merge, can't remember the details), not sure how much you have changed during the merge |
|
From: Wizou <sou...@wi...> - 2010-07-09 16:55:55
|
I didn't change too much Jim Park's code concerning reading from files. Anders a écrit : > Well, I have compiled the unicode version in the past on vc6 (The Jim > Park fork IIRC, possibly from main svn early in the merge, can't > remember the details), not sure how much you have changed during the merge > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > ------------------------------------------------------------------------ > > _______________________________________________ > Nsis-devel mailing list > Nsi...@li... > https://lists.sourceforge.net/lists/listinfo/nsis-devel > |
Thanks for helping keep SourceForge clean.
X