Comments (5)
If you are using the project as base for your own one, just point the import project to the correct location of the .targets
file pulled by NuGet. They are located in the bin
directory of the package. This manual fixup is necessary because of #26, which is fixed, but the fix has not been yet released.
from fslexyacc.
Thanks @kkm000. You say " just point the import project to the correct location". How do I do that ? I am really willing to make FsLexYacc work in a simple setting (whatever it is) so that I can grow it with my already prepared .fsl and .fsy files. I understand that the port from F# PowerPack to distinct F# github projects needs some time to settle down. Please give me an hint to fix the simplest setting ever that would avoid me MSBUILD and VS proj technical pitfalls that I have no knowledge and experience of.
Regards,
FZed
from fslexyacc.
As per FsLexYacc (http://fsprojects.github.io/FsLexYacc/) main page, there is a discrepancy between example files and project files. They link respectively to two different projects on github tests directory, namely :
- LexAndYaccMiniProject
- TestProjectUsingNugetPackage
which have not the same Import logic in their fsproj file.
It would be greatly appreciated to fix this state even before a template is created as requested by @kkm000 in issue opened today.
I have tried to understand the logic of fsproj Import with no success ; I would like to help but I am clueless (see my detailed attempt below).
Have a great week.
Details :
My last attempt was to download all FsLexYacc to local directory then open TestProjects solution with VS 2013 Community.
I get the following error message :
C:\Users\C\Documents\Visual Studio 2013\Projects\myLexTests\FsLexYacc-master\tests\JsonLexAndYaccExample\JsonLexAndYaccExample.fsproj : error : The imported project "C:\Users\C\Documents\Visual Studio 2013\Projects\myLexTests\FsLexYacc-master\bin\Debug\FsLexYacc.targets" was not found.
Confirm that the path in the declaration is correct, and that the file exists on disk. C:\Users\C\Documents\Visual Studio 2013\Projects\myLexTests\FsLexYacc-master\tests\JsonLexAndYaccExample\JsonLexAndYaccExample.fsproj
from fslexyacc.
My bad : I did not build FsLexYacc solution properly and went directly to build TestProjects. Now both builds are successful but I had to modify some lines in the .fsproj in the second test project (mini) so that to make it similar to the first one (Json).
Still, @kkm000 initiative to open issue #32 makes a lot of sense.
I close this issue.
Thanks,
FZed
from fslexyacc.
@FZed, you do not actually need to build this whole repository to use FsLex and FsYacc. You can start with the test project, just copy it alone into a solution by itself. Then, go ahead and add a NuGet package FsLexYacc (it will also pull some dependencies). After you do that, all necessary binaries and runtimes will be downloaded. Then, open the .fsproj file in any editor (e. g., notepad) and change the path to the .targets file. Find the line which mentions Debug\FsLexYacc.targets
and change it to look like
<Import Project="..\..\packages\FsLexYacc.6.0.4\build\FsLexYacc.targets" />
Adjust the number of ..
so that the path corresponds to the location of the file pulled by NuGet.
After you save the .fsproj
file, VS will reload it. That's all it takes. Reopen if this does not do the trick for you.
from fslexyacc.
Related Issues (20)
- A local version of the site is mistakenly published HOT 1
- Links in documentation website are broken HOT 1
- Using F# keywords for non terminal names does not compile HOT 4
- FsLexYacc broken under .net 5.0 runtime only HOT 7
- Emit tables for better diagnostics
- Reductions table being recreated on each parser invocation
- Variables in supplied ".target" file seems undefined leading to compilation error HOT 6
- Activating case insensitive option crash the lexer generator HOT 12
- Building a project which uses FsLex/FsYacc fails when building with Visual Studio 2019 HOT 2
- Publish the ASTs and parsers for the ASTs for the FsLex and FsYacc tools to enable more robust editor tooling HOT 13
- Not an issue more like an optimization HOT 2
- Can't find the FSharp.Text.Lexing and FSharp.Text.Parsing lib? HOT 1
- Invite you to try a new series of Lex/Yacc tools HOT 9
- a syntax highlighter for fslex, fsyacc, F#
- Question: Can we get FSLex to embed a comment with the date-time that the outputs were generated? HOT 1
- Invite you to try FslexFsyacc HOT 7
- How to turn on runtime debug output
- How to get a position of a token from ParseErrorContext HOT 1
- API Documentation issues
- %% Trailer seems not supported
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from fslexyacc.