jade-plugins-devs — Developers Mailing List

Re: [Jade-plugins-devs] Patch for jade-native-msvc to use response files for the linker.

[Frederic S. <fr...@jf...>]

Thanks a lot for this.
I just came back from vacation, so I'll integrate your patch soon.

Fred.

2009/7/31 Juan Jesús García de Soria Lucena <ska...@gm...>

> Hi everybody.
>
>
> When trying to compile Xerces-C 3.0.1 with the Jade Native Plugin and
> Microsoft Visual Studio 2005, I've hit a well-beyond-16kB command line
> for the linker. This totally failed for me.
>
> I attach a patch that moves the MSVC linker command line to use a
> responseFile file in the output directory, into which the command line
> arguments are written. This is then passed to the linker as only one
> "object file" like @<path-to-responseFile>.
>
> This made the compilation work for me.
>
> I would suggest extending this kind of mechanism to the base linker
> class, allowing the derived class to specify whether it supports
> response files or not. This would be useful since gcc-mingw in Windows
> is subjected to the same command line length limits, but GNU tools
> seem to have supported @-based response files in order to overcome
> this for a long time. Please see
> http://gcc.gnu.org/wiki/Response_Files.
>
>
> Best regards,
>
>   Juan Jesus.
>
> --
> Dream small if success is enough for you; dream big if you need to
> change the world.
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus
> on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Jade-plugins-devs mailing list
> Jad...@li...
> https://lists.sourceforge.net/lists/listinfo/jade-plugins-devs
>
>


-- 
JFrog Ltd
5 Habonim st., P.O.Box 8187
Netanya, Israel 42504.
Tel: +972 9 8941444
Fax: +972 9 8659977
http://www.jfrog.org/
http://freddy33.blogspot.com/
http://nothingisinfinite.blogspot.com/

[Jade-plugins-devs] Patch for jade-native-msvc to use response files for the linker.

[Juan J. G. de S. L. <ska...@gm...>]

Hi everybody.


When trying to compile Xerces-C 3.0.1 with the Jade Native Plugin and
Microsoft Visual Studio 2005, I've hit a well-beyond-16kB command line
for the linker. This totally failed for me.

I attach a patch that moves the MSVC linker command line to use a
responseFile file in the output directory, into which the command line
arguments are written. This is then passed to the linker as only one
"object file" like @<path-to-responseFile>.

This made the compilation work for me.

I would suggest extending this kind of mechanism to the base linker
class, allowing the derived class to specify whether it supports
response files or not. This would be useful since gcc-mingw in Windows
is subjected to the same command line length limits, but GNU tools
seem to have supported @-based response files in order to overcome
this for a long time. Please see
http://gcc.gnu.org/wiki/Response_Files.


Best regards,

   Juan Jesus.

-- 
Dream small if success is enough for you; dream big if you need to
change the world.

[Jade-plugins-devs] New juice maven2 proxy

[Frederic S. <fre...@gm...>]

I changed the pom.xml of mvn-anno-mojo and jade-plugins to use juice maven2
proxy.

To activate it a "juice" profile needs to be activated.
So run "mvn -P juice [whatever]" or add juice as default active profile in
your settings.xml.

Thanks.

[Jade-plugins-devs] Usage of settings.xml with jade-plugins

[Frederic S. <fre...@gm...>]

If you want to deploy the plugins to sourceforge, please add these lines to
your maven2 settings.xml:
        <server>
            <id>sourceforge.net</id>
            <username>[sourceforge user name]</username>
            <password>[sourceforge password]</password>
            <filePermissions>664</filePermissions>
            <directoryPermissions>775</directoryPermissions>
        </server>

For Windows users you need to add also to the above server tag:
<configuration>
  <sshExecutable>plink</sshExecutable>
  <scpExecutable>pscp</scpExecutable>
</configuration>

It is important or we will not be able to deploy after you (no group write
access files in the sourceforge server).

Thanks.