kicad-developers team mailing list archive
-
kicad-developers team
-
Mailing list archive
-
Message #01909
Re: adding support for MS visual C++ 2005
-
To:
kicad-devel@xxxxxxxxxxxxxxx
-
From:
kajdas <kajdas@...>
-
Date:
Mon, 27 Oct 2008 22:10:51 -0700
-
A=fbe/bfngjy5q1sj0h5eeja==:
17 a=waejbOB2AAAA:8 a=IEFicb3-OKPNYo9taJgA:9
-
A=veipiak3tvei40lxesjbdgtg_uga:
4 a=MSl-tDqOz04A:10 a=9XSpoOj3B7kA:10
-
Cc:
eadthemm <padamsn@...>
-
In-reply-to:
<ge5vg9+4uum@eGroups.com>
-
Sensitivity:
Normal
As far as I know, this project does not support commercial compilers and it is strongly against using them. This is not in line with open-source and free-software ideology.
If you want to document compiling with one of those compilers, that is probably fine.
You may want to search previous threads regarding this subject.
Martin
---- eadthemm <padamsn@...> wrote:
> I am currently makeing modifications to bring my copy of code to be
> compatable with visual c++ 2005.
>
> the prob i have is round is used everywhere and is posix only.
>
>
> my oringal solution
>
> #ifdef _MSC_VER//add support for round under visual C++ 2005 express
> #ifndef _MSC_VER_FIX_
> double round(double x){return(floor(x+0.5));}
> float round(float x){return(floor(x+0.5));}
> long double round(long double x){return(floor(x+0.5));}
> #define _MSC_VER_FIX_
> #endif
> #endif
>
> placed in fctsys.h because it was a high lvl header and coverd
> everythign that had used round
>
> but this didnt agree with the linker not a prob i have had before on
> other projects.
>
> so adding the above code block to each file using round works but is
> a bit nasty as thers multiple copys of it now.
>
> is there another header file that would be better.
> would it be better to simply change round to floor(x+0.5)
> i went to using this method now
>
> my thougts are of possably commiting the changes and a build guide for
> visual c++ one day so i am asking what would be the best accepted
> practice for this with this project.
>
> current progress log so far http://final.servegame.com/kicad.changelog.log
>
Follow ups
References