On Wed, 7 Sep 2011, cnook wrote:
> Dear Mr. Vincent Torri > > Hello > > When it comes to the following, can we use the mingw-langinfo? > Or.. have to use the evil_langinfo? it would be best to use evil_langinfo. If it is not sufficient, maybe improving it. As I don't know the status, nor the licence of mingw_langinfo, i prefor to not use it. > And I have one more question. > If someone have installed library mingw-langinfo properly and > previously before the building Evil, > then he/she would get a build error when he/she try to build the module Evil. > Because of multiple definition. > > For building module Evil, the clean(ie, just installed) MinGW > environment is necessary. > How about your opinion? Is there any solution for this(multiple > definition error) first, i think that mingw langinfo header should be included before evil one. Hence, i would fix with guards the evil_langinfo header Vincent ------------------------------------------------------------------------------ Doing More with Less: The Next Generation Virtual Desktop What are the key obstacles that have prevented many mid-market businesses from deploying virtual desktops? How do next-generation virtual desktops provide companies an easier-to-deploy, easier-to-manage and more affordable virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
