#reactos-dev requires asking permission to speak, as a means to avoid
spam. You can ask on #reactos, or you can send a private message to
someone.

On 9 August 2015 at 18:48, Alberto Vaudagna <alberto.vaudagna@gmail.com> wrote:
> Hi, I join the reactOs dev chat #ReactOS-Dev but when I try to send a
> message the client (I'm using the web interface webchat.freenode.net) give
> me an error saying I cannot send the message. Do I need to be verify my
> account against the reactos account?
>
> Any way If I run the configure without params from a VS command line I get
> errors about missing CMAKE_PROGRAM is not set. Do I need the react os build
> tools?
>
>
> 2015-08-07 10:22 GMT+02:00 Alberto Vaudagna <alberto.vaudagna@gmail.com>:
>>
>> At least in that way we know it work. I have arleady test it!
>>
>> 2015-08-07 0:21 GMT+02:00 Alberto Vaudagna <alberto.vaudagna@gmail.com>:
>>>
>>> Yes better.
>>> But at the end I think is better build with mingw.
>>>
>>> 2015-08-07 0:10 GMT+02:00 David Quintana (gigaherz) <gigaherz@gmail.com>:
>>>>
>>>> Would you want to pop into our IRC channel so we can troubleshoot in
>>>> realtime?
>>>>
>>>> On 6 August 2015 at 23:56, Alberto Vaudagna <alberto.vaudagna@gmail.com>
>>>> wrote:
>>>> > ya the host files compile fine. but for example the kernel not build
>>>> > give me
>>>> > only linker error. I arleady generate the solution files using the
>>>> > configure
>>>> > script.
>>>> > As I see allmost all of the linking the problem comes from the
>>>> > functions
>>>> > that are implemented in assembly.
>>>> > Don't know.
>>>> >
>>>> > 2015-08-06 23:50 GMT+02:00 David Quintana (gigaherz)
>>>> > <gigaherz@gmail.com>:
>>>> >>
>>>> >> In theory, yes, but in practice not everything required is built by
>>>> >> the smaller .sln files, so it's best to compile the large one at the
>>>> >> root, but remember to always first build host-tools, otherwise
>>>> >> nothing
>>>> >> will work since the host-tools are necessary to build the rest.
>>>> >>
>>>> >> On 6 August 2015 at 23:30, Alberto Vaudagna
>>>> >> <alberto.vaudagna@gmail.com>
>>>> >> wrote:
>>>> >> > And get errors using msbuild. I should go into the build folder and
>>>> >> > for
>>>> >> > example I want compile the kernel. I go into the kernel folder and
>>>> >> > write
>>>> >> > msbuild NTOS.sln, right?
>>>> >> >
>>>> >> > 2015-08-06 23:26 GMT+02:00 Alberto Vaudagna
>>>> >> > <alberto.vaudagna@gmail.com>:
>>>> >> >>
>>>> >> >> I mean build inside vs. It would be very great. But I have no
>>>> >> >> problem
>>>> >> >> building with mingw.
>>>> >> >> Ah never know that msbuild work.
>>>> >> >> Thanks for the response!
>>>> >> >>
>>>> >> >> 2015-08-06 23:21 GMT+02:00 David Quintana (gigaherz)
>>>> >> >> <gigaherz@gmail.com>:
>>>> >> >>>
>>>> >> >>> I don't get any error locally, it may be that your build folder
>>>> >> >>> became
>>>> >> >>> corrupted. It happens every now and then, that a file is out of
>>>> >> >>> date,
>>>> >> >>> but the build system doesn't realize it.
>>>> >> >>>
>>>> >> >>> Unless you mean building from INSIDE visual studio... that's not
>>>> >> >>> currently a supported build method, I believe. You can use
>>>> >> >>> msbuild
>>>> >> >>> (the same build system used by visual studio) from a cmd window,
>>>> >> >>> and
>>>> >> >>> that should work, or use the primary way of building, using
>>>> >> >>> ninja,
>>>> >> >>> which is also the fastest method of all.
>>>> >> >>>
>>>> >> >>> On 6 August 2015 at 22:10, Alberto Vaudagna
>>>> >> >>> <alberto.vaudagna@gmail.com>
>>>> >> >>> wrote:
>>>> >> >>> > Just wonder why no one has yet fixed the compiling errors you
>>>> >> >>> > get if
>>>> >> >>> > you use
>>>> >> >>> > visual studio.
>>>> >> >>> > All the errors are not code related but linking problem, so I
>>>> >> >>> > wonder
>>>> >> >>> > why no
>>>> >> >>> > body solve all the compiler errors.
>>>> >> >>> > Thanks,
>>>> >> >>> > Alberto Vaudagna
>>>> >> >>> >
>>>> >> >>> > _______________________________________________
>>>> >> >>> > Ros-dev mailing list
>>>> >> >>> > Ros-dev@reactos.org
>>>> >> >>> > http://www.reactos.org/mailman/listinfo/ros-dev
>>>> >> >>>
>>>> >> >>> _______________________________________________
>>>> >> >>> Ros-dev mailing list
>>>> >> >>> Ros-dev@reactos.org
>>>> >> >>> http://www.reactos.org/mailman/listinfo/ros-dev
>>>> >> >>
>>>> >> >>
>>>> >> >
>>>> >> >
>>>> >> > _______________________________________________
>>>> >> > Ros-dev mailing list
>>>> >> > Ros-dev@reactos.org
>>>> >> > http://www.reactos.org/mailman/listinfo/ros-dev
>>>> >>
>>>> >> _______________________________________________
>>>> >> Ros-dev mailing list
>>>> >> Ros-dev@reactos.org
>>>> >> http://www.reactos.org/mailman/listinfo/ros-dev
>>>> >
>>>> >
>>>> >
>>>> > _______________________________________________
>>>> > Ros-dev mailing list
>>>> > Ros-dev@reactos.org
>>>> > http://www.reactos.org/mailman/listinfo/ros-dev
>>>>
>>>> _______________________________________________
>>>> Ros-dev mailing list
>>>> Ros-dev@reactos.org
>>>> http://www.reactos.org/mailman/listinfo/ros-dev
>>>
>>>
>>
>
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev

_______________________________________________
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev