-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build on Windows #50
Comments
OK. I am using Visual studio 2022 and I don't have issues there, not sure what the differences are? |
I build the source on on Windows 10 Pro. the .h files are for Linux. Can you build on windows without problem? |
Yes I build on Windows 10 with Visual studio 2022.. One of these days I'll try to move away from Visual studio as it is unnecessary complexity for just a command line application. But it will probably take a while before this happens |
when I built scream in Visual studio 2019 on windows pro, I opened build and selected batch build, in the opened window L selected ALL_Build, scream_bw_test_tx, scream_bw_test_rx, or ZERO_CHECK with release, debug, minSizeRel or RelWithDegInfo and tried all options, I got error: "sys/socket.h": No such file or directory. When I changed it and I got sys/time.h. error. I changed again the source, I got error No such file or directory for sys/time.h, netinet/in.h pthread.h and so on. How do you build scream on windows? Do you mean that you will change something this week, so that I can build on windows? I need scream to be compiled on windows recently. I am waiting for your reply after your change. |
Hi
Have you tried to open up scream.sln in Vidual Studio and build ?
/Ingemar
From: wendych864 ***@***.***>
Sent: Monday, 13 February 2023 10:29
To: EricssonResearch/scream ***@***.***>
Cc: Ingemar Johansson S ***@***.***>; Comment ***@***.***>
Subject: Re: [EricssonResearch/scream] build on Windows (Issue #50)
when I built scream in Visual studio 2019 on windows pro, I opened build and selected batch build, in the opened window L selected ALL_Build, scream_bw_test_tx, scream_bw_test_rx, or ZERO_CHECK with release, debug, minSizeRel or RelWithDegInfo and tried all options, I got error: "sys/socket.h": No such file or directory. When I changed it and I got sys/time.h. error. I changed again the source, I got error No such file or directory for sys/time.h, netinet/in.h pthread.h and so on. How do you build scream?
—
Reply to this email directly, view it on GitHub<https://protect2.fireeye.com/v1/url?k=31323334-501d5122-313273af-454445555731-8749944efefc22b8&q=1&e=55dc614e-004c-4134-9e8b-12c66bcf29a1&u=https%3A%2F%2Fgithub.com%2FEricssonResearch%2Fscream%2Fissues%2F50%23issuecomment-1427613318>, or unsubscribe<https://protect2.fireeye.com/v1/url?k=31323334-501d5122-313273af-454445555731-4ff41f460ab652ac&q=1&e=55dc614e-004c-4134-9e8b-12c66bcf29a1&u=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACRZ2GCQHFA6SLNKY4277PTWXH5G7ANCNFSM6AAAAAAUXRIOK4>.
You are receiving this because you commented.Message ID: ***@***.******@***.***>>
|
Yes, I opened scream.sln and the source code are opened in visual studio. Then I selected "Build" menu, then "batch build", Then I saw an opened small window with ALL_Build, scream_bw_test_tx, scream_bw_test_rx, or ZERO_CHECK with release, debug, minSizeRel or RelWithDegInfo options. I selected some of them and then clicked on "build". There were then errors"sys/socket.h": No such file or directory. How do you build? |
Hi
Can you try with Visual Studio 2022 ?
/I
From: wendych864 ***@***.***>
Sent: Tuesday, 14 February 2023 10:57
To: EricssonResearch/scream ***@***.***>
Cc: Ingemar Johansson S ***@***.***>; Comment ***@***.***>
Subject: Re: [EricssonResearch/scream] build on Windows (Issue #50)
Yes, I clicked on scream.sln and it is opened in visual studio. Then I selected "Build" menu, then "batch build", Then I saw an opened small window with ALL_Build, scream_bw_test_tx, scream_bw_test_rx, or ZERO_CHECK with release, debug, minSizeRel or RelWithDegInfo options. I selected some of them and then clicked on "build". There were then errors"sys/socket.h": No such file or directory. How do you build?
—
Reply to this email directly, view it on GitHub<https://protect2.fireeye.com/v1/url?k=31323334-501cfaf3-313273af-454445554331-def3536946dc866a&q=1&e=40406c3b-5f0a-4ca6-9d35-9c94693085f7&u=https%3A%2F%2Fgithub.com%2FEricssonResearch%2Fscream%2Fissues%2F50%23issuecomment-1429445218>, or unsubscribe<https://protect2.fireeye.com/v1/url?k=31323334-501cfaf3-313273af-454445554331-399c260f5d0b27aa&q=1&e=40406c3b-5f0a-4ca6-9d35-9c94693085f7&u=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACRZ2GBNY74IGMIUWTP27TLWXNJFRANCNFSM6AAAAAAUXRIOK4>.
You are receiving this because you commented.Message ID: ***@***.******@***.***>>
|
I can build scream in Visual Studio 2022 without error. In build menu, I selected batch build, a batch build window with scream_01 release/Win32, debug/win32 appeared. When I selected release/win32 and debug/win32 and then clicked on build, release/scream_01 und debug/scream_01 are created. But there is no release/win64 and debug/win64 in the batch build window. My Windows 10 pro ist win64. Is this right? Have I built rightly? On mac a sender and receiver are created, for example scream_bw_test_tx and scream_bw_test_rx are created. On Windows only scream_01 created. Is this right? how can I run scream_01 as sender and receiver? |
OK. I believe now I understand.. The visual studio project only builds a simple simulator that is mostly used to verify that the ScreamTx and ScreamRx is correctly implemented. The scream_bw_test_tx and scrream_bw_test_rx does not currently build on windows |
Have you tried with the GStreamer Rust plugin
scream/gstscream at master · EricssonResearch/scream (github.com)<https://github.com/EricssonResearch/scream/tree/master/gstscream>
I have not had the opportunity to try it on Windows.
/Ingemar
From: wendych864 ***@***.***>
Sent: Tuesday, 21 February 2023 09:44
To: EricssonResearch/scream ***@***.***>
Cc: Ingemar Johansson S ***@***.***>; Comment ***@***.***>
Subject: Re: [EricssonResearch/scream] build on Windows (Issue #50)
Do you think that we can build scream on windows without to change the source code of scream? sys/socket etc are not for windows. Or we must change the source code for windows? What do you think the best way to build scream on windows?
—
Reply to this email directly, view it on GitHub<https://protect2.fireeye.com/v1/url?k=31323334-501cfaf3-313273af-454445554331-7f03c00a1e702838&q=1&e=e3bbdb4d-654a-419e-9828-1bd19fcef9fe&u=https%3A%2F%2Fgithub.com%2FEricssonResearch%2Fscream%2Fissues%2F50%23issuecomment-1438062710>, or unsubscribe<https://protect2.fireeye.com/v1/url?k=31323334-501cfaf3-313273af-454445554331-bf19d85b1de3b901&q=1&e=e3bbdb4d-654a-419e-9828-1bd19fcef9fe&u=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACRZ2GC6UWVOPD4ZAXRWXTTWYR56BANCNFSM6AAAAAAUXRIOK4>.
You are receiving this because you commented.Message ID: ***@***.******@***.***>>
|
Do you think that we can build scream on windows without to change the source code of scream? sys/socket etc are not for windows. Or we must change the source code for windows to build scream successfully? What do you think the best way to build scream on windows? |
I built GStreamer Rust plugin and there are 2 errors. Followings are built information:
near the top of the file, but after cmake_minimum_required(). CMake is pretending there is a "project(Project)" command on the first CMake Warning (dev) in CMakeLists.txt: -- Selecting Windows SDK version 10.0.22000.0 to target Windows 10.0.19045.
should be added at the top of the file. The version specified may be lower -- Configuring done (0.1s) error[E0425]: cannot find function For more information about this error, try error[E0425]: cannot find function For more information about this error, try |
I checkout the source code from master and offen the .sln file in visual studio community 2017. I build the source code. But there is many errors, e. g. sys/socket.h, sys/time.h netinet/in.h, pthread.h no such file or drectory. sys/time.h etc seems for Linux. I corrected these errors and install vcpkg, Then there are also other errors.
The text was updated successfully, but these errors were encountered: