Thorbjørn,
When you figure this out can you please write up the summary so we can
put it on the project webpages?
Thanks
Tim
Thorbjørn Ravn Andersen wrote:
Gregory Shimansky skrev den 07-07-2006 15:01:
Do you mean you have an error that there is no manifest file present?
This has
been
Tim Ellison skrev den 10-07-2006 10:41:
Thorbjørn,
When you figure this out can you please write up the summary so we can
put it on the project webpages?
Sure, but just copying all the manifests did not work, so right now I
have - temporarily - given up.
Where are all the Visual Studio
Hmm..
Let me go check previous mails. I think I can be of some help here...
Regards,
Sanket
-Original Message-
From: Thorbjørn Ravn Andersen [mailto:[EMAIL PROTECTED]
Sent: Mon 7/10/2006 4:16 PM
To: harmony-dev@incubator.apache.org
Subject: Re: Strategy for Harmony to work with Visual
OK. Security is always good.
But I think that it is better to use C99 functions mentioned by Ivan.
I've checked that snprintf function is implemented in glibc and MSVS 2003.
SY, Alexey
2006/7/10, Xiao-Feng Li [EMAIL PROTECTED]:
My idea is NOT to write wrappers for Microsoft extentions.
Can someone just collect the info that is known and summarize? I'd
prefer a document for the website, but if you'd rather work on the wiki
and we can harvest from there later, that works for me as well...
geir
Sanket Sharma wrote:
Hmm..
Let me go check previous mails. I think I can be of
I think that creating such wrappers and implementing non standard MS
extensions for another platforms is not a good idea. What will we do
if this extension will not be accepted? Rewrite everything again?
I agree that such extension is probably good. But we should wait until
community will accept
My idea is NOT to write wrappers for Microsoft extentions. First, they
are to enhance our own C code safety with more checkings; second, they
are not MS extensions. The only thing is, they are enlighted by and
have similar APIs as MS's safe CRT.
Thanks,
xiaofeng
On 7/9/06, Alexey Petrenko
Matt Benson skrev den 06-07-2006 19:25:
Some particulars may be slightly different from one
machine to the next, but in general this works; we
need to get this info in the wiki IMHO
Agreed. I have starting to write such an entry, but is currently
stopped by the VSMCR8.DLL problem of VS2005
On Friday 07 July 2006 16:00 Thorbjørn Ravn Andersen wrote:
Matt Benson skrev den 06-07-2006 19:25:
Some particulars may be slightly different from one
machine to the next, but in general this works; we
need to get this info in the wiki IMHO
Agreed. I have starting to write such an
Gregory Shimansky skrev den 07-07-2006 15:01:
Do you mean you have an error that there is no manifest file present?
This has
been answered too in the same threads about using VC 8.0. I just copied all
the manifests created in native-src/win.IA32 to deloy/jdk/jre/bin manually to
see if it
Xiao-Feng Li wrote:
Visual Studio 2005 (Whidbey VC8) C runtime library (CRT) has changed
some compilation rules and APIs for better security or ISO/ANSI
conformance. Many changes are breaking, i.e., incompatible. For
example, it adds safer counterparts for many functions like `strcpy_s'
for
Ok, then I will get back to VC7 at the moment. :-) Let's wait till
its acceptance by the community.
Actually I don't see them as new APIs; instead, I view them as
enforced good coding conventions that help to achieve better security,
e.g., always check the buffer size in debug mode. (Personally
Don't take my word here - we need opines from others, especially the
people that work a lot on windows...
geir
Xiao-Feng Li wrote:
Ok, then I will get back to VC7 at the moment. :-) Let's wait till
its acceptance by the community.
Actually I don't see them as new APIs; instead, I view
This particular mail (by Gregory) contains
(a) a link to another mail (of his) describing how to
get the MSFT tools to work, and
(b) a link to a JIRA issue containing the necessary
patches to use NASM for assembly:
http://mail-archives.apache.org/mod_mbox/incubator-harmony-dev/200606.mbox/[EMAIL
On Thursday 06 July 2006 14:35 Xiao-Feng Li wrote:
Ok, then I will get back to VC7 at the moment. :-) Let's wait till
its acceptance by the community.
Actually I don't see them as new APIs; instead, I view them as
enforced good coding conventions that help to achieve better security,
e.g.,
On 7/6/06, Geir Magnusson Jr [EMAIL PROTECTED] wrote:
I think the key reason is that this is non-standard stuff from
microsoft's for-fee toolchain, and people in OSS try to avoid having a
dependency on that.
I wouldn't mind supporting this at some point a) once it becomes a
standard and b) has
On 7/6/06, Xiao-Feng Li [EMAIL PROTECTED] wrote:
Visual Studio 2005 (Whidbey VC8) C runtime library (CRT) has changed
some compilation rules and APIs for better security or ISO/ANSI
conformance. Many changes are breaking, i.e., incompatible. For
example, it adds safer counterparts for many
I would suggest another approach.
Since the safe CRT APIs are mostly similar to the original counterpart
but enforcing safety checks and validations, we can take them as
coding conventions, so as to achieve both the safety and portability.
For example, with strcpy, we do this way:
step 1.
The checks in my code example below can be asserts or defined for
debug mode only, if people worry about the performance AND are almost
sure about the safety. But I don't think they are only for debugging
purpose. Optimizations can be done to reduce the overhead.
Thanks,
xiaofeng
On 7/7/06,
Xiao-Feng Li wrote:
It has lots of secure enhancement API changes. What's the strategy
for those APIs support in Harmony?
Huh? What APIs in Visual Studio?
geir
-
Terms of use :
20 matches
Mail list logo
