<p>Hi, I am using vs + cmake + rebar. C++ part is buit with cmake + vs and rest erlang code is buit with rebar. All build procedures is made from one build.bat file. Works well.</p>
<div class="gmail_quote">13.05.2012 18:16 пользователь "Daniel Goertzen" <<a href="mailto:dang@networkintegritysystems.com">dang@networkintegritysystems.com</a>> написал:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I am also unable to make rebar work on Windows. Whenever I download<br>
something with a rebar script, I have to basically open it in an<br>
editor "execute" it by hand and hack everything into place... even for<br>
straight forward things with no C compiling like gproc. No fun at<br>
all.<br>
<br>
I settled for cygwin Make, and I was able to build a working NIF<br>
module using the compile command indicated in the NIF tutorial. The<br>
Makefile is completely Windows specific, but it meets my needs. This<br>
of course uses Visual Studio... which is a free download and really<br>
not a big deal to install.<br>
<br>
Dan.<br>
<br>
On Sun, May 13, 2012 at 8:07 AM, Tony Rogvall <<a href="mailto:tony@rogvall.se">tony@rogvall.se</a>> wrote:<br>
> Dear erlang-ers.<br>
><br>
> Is there anyone on this list that do develop on windows ?<br>
> How on earth do you do that ? ;)<br>
><br>
> I am trying to get a driver compiled using rebar.<br>
> rebar is nearly working on MingW but git is not available for MingW, the<br>
> reason is somewhat bizarre ...<br>
> rebar is nearly working on cygwin but there is some path problem that result<br>
> in "access denied".<br>
><br>
> Right now I reverted to using a Makefile with MingW, that after lots of copy<br>
> and past finally works.<br>
><br>
> Is rebar supposed to be working with cygwin/mingw ?<br>
><br>
> BTW<br>
> I will NOT install Visual Studio XYZ :-)<br>
> Thanks<br>
><br>
> /Tony<br>
><br>
> "Installing applications can lead to corruption over time. Applications<br>
> gradually write over each other's libraries, partial upgrades occur, user<br>
> and system errors happen, and minute changes may be unnoticeable and<br>
> difficult to fix"<br>
><br>
><br>
><br>
><br>
> _______________________________________________<br>
> erlang-questions mailing list<br>
> <a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
> <a href="http://erlang.org/mailman/listinfo/erlang-questions" target="_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><br>
><br>
<br>
<br>
<br>
--<br>
Daniel Goertzen | Senior Software Engineer<br>
Office: 828.610.4596 | Fax: 828.322.5294 | <a href="mailto:dang@networkintegritysystems.com">dang@networkintegritysystems.com</a><br>
Network Integrity Systems | We Bring Security To Light™<br>
<br>
1937 Tate Blvd. SE<br>
<br>
Hickory, North Carolina, USA 28602<br>
<br>
Network Integrity Systems’ INTERCEPTOR™ Optical Network Security<br>
System is a Smart-PDS™ that ensures superior protection and cost<br>
effectiveness of classified networks. For more information, visit our<br>
website at:<a href="http://www.networkintegritysystems.com" target="_blank">www.networkintegritysystems.com</a>.<br>
<br>
<br>
__________________________________________<br>
INTERCEPTOR™ Optical Network Security System is made in the USA for<br>
the USA. Although not an export controlled item, because of the role<br>
it plays in the assurance of the safety and integrity of National<br>
Security Information, Network Integrity Systems (NIS) is committed to<br>
compliance with the U.S. Export Administration Act. Accordingly, NIS<br>
will not ship INTERCEPTOR products to certain foreign government end<br>
users without U.S. government approval and will refuse transactions<br>
with individuals or entities that have been denied export privileges.<br>
_______________________________________________<br>
erlang-questions mailing list<br>
<a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
<a href="http://erlang.org/mailman/listinfo/erlang-questions" target="_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><br>
</blockquote></div>