DO NOT REPLY [Bug 24061] - jsharpc does not work well with a big number of source files.

2003-12-18 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24061.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24061

jsharpc does not work well with a big number of source files.

[EMAIL PROTECTED] changed:

   What|Removed |Added

Version|1.6Beta |1.6.0

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 24061] - jsharpc does not work well with a big number of source files.

2003-10-24 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24061.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24061

jsharpc does not work well with a big number of source files.

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||DUPLICATE



--- Additional Comments From [EMAIL PROTECTED]  2003-10-24 05:43 ---


*** This bug has been marked as a duplicate of 19630 ***

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 24061] - jsharpc does not work well with a big number of source files.

2003-10-23 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24061.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24061

jsharpc does not work well with a big number of source files.





--- Additional Comments From [EMAIL PROTECTED]  2003-10-23 16:31 ---
Ok. This is probably a duplicate of a complaint related to CSC. The problem is
that the command line is too big. The fix would be to pump all the commands
filenames into an @file response file and then exec it; a bit of cleanup of
NetCommand will put all the changes into one place.

but here is a problem related to the C# side of things; I dont think mono
handles the @file inclusion of long commands, so we run a risk of breaking
things there. 

...

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 24061] - jsharpc does not work well with a big number of source files.

2003-10-23 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24061.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24061

jsharpc does not work well with a big number of source files.





--- Additional Comments From [EMAIL PROTECTED]  2003-10-23 16:37 ---
Then do as CppTasks does (or apply I think), and break the command into 
several commands, no? --DD

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: DO NOT REPLY [Bug 24061] - jsharpc does not work well with a big number of source files.

2003-10-23 Thread Stefan Bodewig
On 23 Oct 2003, [EMAIL PROTECTED] wrote:

 but here is a problem related to the C# side of things; I dont think
 mono handles the @file inclusion of long commands, so we run a risk
 of breaking things there.

[EMAIL PROTECTED] jsps]$ mcs --help
Mono C# compiler, (C) 2001 - 2003 Ximian, Inc.
mcs [options] source-files
   --aboutAbout the Mono C# compiler
   -checked[+|-]  Set default context to checked
   -codepage:ID   Sets code page to the one in ID
  (number, `utf8' or `reset')
   -define:S1[;S2]Defines one or more symbols (short: /d:)
   -debug[+-] Generate debugging information
   -doc:FILE  XML Documentation file to generate
   -g Generate debugging information
   --fatalMakes errors fatal
   -lib:PATH1,PATH2   Adds the paths to the assembly link path
   -main:classSpecified the class that contains the entry point
   -noconfig[+|-] Disables implicit references to assemblies
   -nostdlib[+|-] Does not load core libraries
   -nowarn:W1[,W2]Disables one or more warnings
   -out:FNAME Specifies output file
   --parseOnly parses the source file
   --expect-error X   Expect that error X will be encountered
   -recurse:SPEC  Recursively compiles the files in SPEC ([dir]/file)
   -reference:ASS References the specified assembly (-r:ASS)
   --stacktrace   Shows stack trace at error location
   -target:KIND   Specifies the target (KIND is one of: exe, winexe,
  library, module), (short: /t:)
   --timestampDisplays time stamps of various compiler events
   -unsafe[+|-]   Allows unsafe code
   -warnaserror[+|-]  Treat warnings as errors
   -warn:LEVELSets warning level (the highest is 4, the default)
   -v Verbose parsing (for debugging the parser)

Resources:
   -linkresource:FILE[,ID] Links FILE as a resource
   -resource:FILE[,ID] Embed FILE as a resource
   --mcs-debug X  Sets MCS debugging level to X
   @file  Read response file for more options

Options can be of the form -option or /option

Stefan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]